refactor: separate tool catalog from manager

CHANGELOG.md

@@ -69,6 +69,8 @@ under **Unreleased** until a new version is selected and published.
 - Consolidated tool schemas, execution handlers, Doris OAuth policy, safe
   audit metadata, compatibility aliases, and generated documentation in one
   validated Tool Definition Registry.
+- Separated immutable tool metadata into a standalone catalog while keeping
+  lifecycle, authorization, audit, and execution routing in the tools manager.
 - Positioned Dynamic Client Registration as a compatibility fallback behind
   preconfigured clients and Client ID Metadata Documents.
 - Persisted static bearer tokens as self-describing SHA-256/SHA-512 digests,

README.md

@@ -1518,11 +1518,14 @@ async def _your_new_analysis_tool(
 
 ### 3. Add the Registry Definition
 
-Add one `Tool` schema to `DorisToolsManager._build_tool_registry`, then classify
-its policy once in `doris_mcp_server/tools/tool_registry.py`. Do not add a
-decorator wrapper or an `if/elif` dispatch branch:
+Add one `Tool` schema to
+`doris_mcp_server/tools/tool_catalog.py::build_tool_registry`, then classify its
+policy once in `doris_mcp_server/tools/tool_registry.py`. Do not add a decorator
+wrapper or an `if/elif` dispatch branch:
 
 ```python
+# In doris_mcp_server/tools/tool_catalog.py
+
 Tool(
     name="your_new_analysis_tool",
     description="Description of your new analysis tool",