Address PR comments.

Author: blkt

docs/toolhive/guides-cli/run-mcp-servers.mdx

@@ -209,16 +209,23 @@ ToolHive cannot find one of the specified tools.
 
 ### Override tool names and descriptions
 
-With ToolHive you can change modify how tools exposed by an MCP server are
-exposed to clients. In particular, tool names and descriptions can be changed.
+With ToolHive you can modify how tools exposed by an MCP server are exposed to
+clients. In particular, tool names and descriptions can be changed.
 
-This can be useful in cases where network policies are applied and tool
-descriptions need to reflect that, or to trick an Agent into calling a specific
-tool when some particular question is asked.
+This is useful when you want to guide an agent toward calling a specific tool
+for particular questions.
 
-Taking the `fetch` MCP server as an example, which exposes a single `fetch` tool
-with the a description like
-`"Fetches a URL from the internet and optionally extracts its contents as markdown."`
+One common use case is running multiple copies of the same MCP server with
+different [network access levels](./network-isolation.mdx)—one for internal
+resources and another for public internet access. By overriding the tool names
+and descriptions, you can help your agent choose the right server for each task.
+
+For example, the `fetch` MCP server exposes a single `fetch` tool with a
+description like:
+
+```
+"Fetches a URL from the internet and optionally extracts its contents as markdown."
+```
 
 You can now change it by supplying a file like the following
 
@@ -233,27 +240,25 @@ You can now change it by supplying a file like the following
 }
 ```
 
-Which must then be passed to `thv run`
+Then pass this file to [`thv run`](../reference/cli/thv_run.md):
 
 ```sh
 thv run --tools-override override.json fetch
 ```
 
-Note that the key of the nested object is the _actual name_ of the tool, while
-the value specified in the nested object is the _overridden name_ that the
-Client will see.
+The key in the override object is the _original tool name_, while the `name`
+field contains the _new name_ that clients will see.
 
 :::info
 
-Additional care must be taken when using `--tools` and `-tools-override`
-together in the same command.
+Take care when using `--tools` and `--tools-override` together in the same
+command.
 
-Tool Filtering and Tool Overrides are mostly orthogonal, with the former
-limiting access to a subset of filters, while the latter changes how the set
-looks like.
+Tool filtering and tool overrides work independently: filtering limits access to
+a subset of tools, while overrides change how those tools appear to clients.
 
-When you want to use both, `--tools` must refer to _overridden names_, i.e. the
-new names you get to define, since that's what the Client will eventually see.
+When using both options, `--tools` must reference the _overridden names_ (the
+new names you define) since those are what clients will see.
 
 :::