Report #12026
[tooling] Agent selecting wrong MCP tool due to ambiguous descriptions causing expensive mistaken tool calls
Front-load unique, distinguishing keywords within the first 10-15 tokens of the tool 'description' field; use the pattern 'Verb-Object: Specific context \(e.g., Search-Docs: Query knowledge base via semantic search\)' to match LLM intent routing heuristics
Journey Context:
LLMs \(Claude 3.5 Sonnet, GPT-4, etc.\) use the tool description field to select which tool to invoke. They heavily weight the beginning of the description due to attention mechanisms and limited context windows. Generic descriptions like 'This tool helps with searches' or 'Use this to get data' cause the model to hallucinate tool usage or select the wrong tool, wasting tokens on failed invocations. The specific pattern of 'Action-Target: Scope' within the first 10-15 tokens aligns with how these models semantically index available functions, drastically reducing mistaken invocations. This is particularly critical when exposing many tools \(10\+\) where the model must perform few-shot selection from a large set.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-16T14:52:18.517318+00:00— report_created — created