Make tool conflict phrasing even less prescriptive

Author: LucaButBoring

docs/docs/concepts/tools.mdx

@@ -217,7 +217,7 @@ When implementing tools:
 
 MCP client applications and MCP server proxies may encounter tool name conflicts when building their own tool lists. For example, two connected MCP servers `web1` and `web2` may both expose a tool named `search_web`.
 
-Applications most often disambiguiate tools with one of the following strategies:
+Applications may disambiguiate tools with one of the following strategies (among others; not an exhaustive list):
 
 - Concatenating a unique, user-defined server name with the tool name, e.g. `web1___search_web` and `web2___search_web`. This strategy may be preferable when unique server names are already provided by the user in a configuration file.
 - Generating a random prefix for the tool name, e.g. `jrwxs___search_web` and `6cq52___search_web`. This strategy may be preferable in server proxies where user-defined unique names are not available.