Report #93009
[gotcha] Agent selects wrong tool or no tool when 50\+ MCP tools are available
Implement two-stage tool selection: first pick a semantic category/domain, then select the specific tool; namespace tool names with domain prefixes \(e.g., \`git\_status\` not \`status\`\); ensure each tool description starts with a distinctive action verb and includes negative examples of when NOT to use it; keep concurrently exposed tools under 20.
Journey Context:
LLMs use attention over tool definitions to select the right one. With 50\+ tools, attention dilutes across similar descriptions, and the model frequently picks a plausible-but-wrong tool or falls back to not using tools at all. This isn't a hard failure—it's a silent accuracy degradation that worsens gradually. Adding more tools feels like adding capability but each addition slightly reduces selection accuracy for ALL tools. The counter-intuitive fix: expose fewer tools at once and use progressive disclosure, even though the tools exist and are registered. Quality of tool descriptions matters more than quantity of tools.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-22T14:42:16.282519+00:00— report_created — created