feat: add tool override for customize tools

Author: samuv

docs/toolhive/guides-ui/customize-tools.mdx

@@ -6,9 +6,10 @@ description:
 ---
 
 ToolHive lets you customize which tools from a running MCP server are available
-to your AI clients. This gives you fine-grained control over the capabilities
-exposed by each server, helping you create focused tool sets and reduce
-complexity for your AI workflows.
+to your AI clients. You can enable or disable individual tools, and customize
+their names and descriptions. This gives you fine-grained control over the
+capabilities exposed by each server, helping you create focused tool sets and
+reduce complexity for your AI workflows.
 
 ## Why customize tools?
 
@@ -22,11 +23,18 @@ Customizing tools helps you:
   risk of unintended actions
 - **Create focused environments**: Tailor tool availability to specific tasks or
   projects
+- **Clarify tool purpose**: Edit tool names and descriptions to make them more
+  understandable for your specific use case
 
-:::info[Registry servers only]
+:::info[Registry match required]
 
-Tool customization is available only for MCP servers installed from the
-registry. Custom local and remote MCP servers do not support this feature.
+Tool customization is only available for MCP servers that match an entry in the
+registry. This includes:
+
+- Servers installed directly from the registry
+- Custom servers with a docker image or URL that matches a registry entry
+
+Custom servers that don't match any registry entry do not support this feature.
 
 :::
 
@@ -69,21 +77,59 @@ all tools on a server, as this would make the server non-functional.
 
 :::
 
+## Edit tool names and descriptions
+
+You can customize the name and description of any tool to make it more suitable
+for your workflow. This is useful when the default tool name or description is
+unclear, or when you want to adapt the tool's presentation to your specific use
+case.
+
+To edit a tool:
+
+1. On the customize tools page, find the tool you want to edit.
+1. Click the **Edit** button next to the tool.
+1. In the dialog that opens:
+   - Edit the **Tool** field to change the tool's name.
+   - Edit the **Description** field to customize the tool's description.
+   - The original values are shown as helper text for reference.
+   - Leave either field empty to reset it to the original value.
+1. Click **Save** to apply your changes, or **Cancel** to discard them.
+
+Tools with custom names or descriptions are marked with a wrench icon to
+indicate they have custom overrides applied. The icon color indicates the
+status:
+
+- **Orange**: The tool has unsaved custom overrides
+- **Primary color**: The tool has saved custom overrides
+
+Your customizations are preserved even if you disable and re-enable the tool.
+
+:::tip[Unsaved custom overrides]
+
+If you customize a tool's name or description but haven't clicked **Apply** on
+the main page, a tooltip appears indicating "This tool has unsaved custom
+overrides". Click **Apply** to save both your tool selection changes and custom
+overrides.
+
+:::
+
 ## How filtering works
 
 When you customize tools:
 
-1. You toggle tools on or off using the switches.
+1. You toggle tools on or off using the switches and optionally edit their names
+   and descriptions.
 1. After clicking **Apply**, your settings are saved to the server
    configuration.
 1. The ToolHive proxy intercepts tool discovery requests from AI clients.
-1. Only enabled tools appear in the client's tool list.
+1. Only enabled tools appear in the client's tool list, with your custom names
+   and descriptions if you've set them.
 1. If a client attempts to call a disabled tool directly, the proxy blocks the
    request.
 
 This filtering happens transparently without requiring any changes to your AI
-client configuration. Your clients automatically see the updated tool list the
-next time they connect.
+client configuration. Your clients automatically see the updated tool list with
+customized names and descriptions the next time they connect.
 
 :::tip
 
@@ -116,17 +162,38 @@ environments:
 1. For example, enable only read-only tools in a production group, while
    allowing all tools in a development group.
 
+### Clarify technical tool names
+
+If an MCP server exposes tools with technical or unclear names:
+
+1. Open **Customize Tools** for the server.
+1. Click **Edit** on tools with unclear names.
+1. Change the tool name to something more descriptive (for example, rename
+   `list_commits_test` to `List Commits`).
+1. Update the description to clarify what the tool does in your context.
+1. Click **Save**, then **Apply**.
+1. Your AI clients now see clearer, more intuitive tool names and descriptions.
+
 ## Reset to defaults
 
-To restore all tools to their default enabled state:
+To restore all tools to their default enabled state and remove custom overrides:
+
+**To reset an individual tool's name or description:**
+
+1. Click the **Edit** button next to the tool.
+1. Clear the **Tool** and **Description** fields (leave them empty).
+1. Click **Save**.
+1. Click **Apply** to save your changes.
+
+The tool name and description revert to their original values, and the wrench
+icon is removed.
+
+**To enable all tools:**
 
 1. Open the customize tools page for the server.
 1. Manually enable all tools using the toggle switches.
 1. Click **Apply** to save your changes.
 
-There is no automatic "reset all" button, but you can quickly enable all tools
-by toggling each switch and clicking **Apply**.
-
 ## Related information
 
 - [Run MCP servers](./run-mcp-servers.mdx)