docs(tools): suggest using config keys as identifiers for servers for disambiguation

Author: LucaButBoring

docs/docs/concepts/tools.mdx

@@ -216,7 +216,7 @@ When implementing tools:
 ### Tool name conflicts
 
 MCP client applications and MCP server proxies may encounter tool name conflicts when building their own tool lists.
-To resolve these conflicts, we recommend maintaining a unique identifier for each connected MCP server, and prefixing that to the tool name with `___` (three underscores) as a separator.
+To resolve these conflicts, we recommend maintaining a unique identifier (such as a config key, in the case of client applications) for each connected MCP server, and prefixing that to the tool name with `___` (three underscores) as a separator.
 
 For example, if two web search MCP servers called `a` and `b` both expose a `search_web` tool, client applications or proxies may consider registering these as `a___search_web` and `b___search_web` to disambiguate them.