Report #97490
[frontier] My MCP-powered agent keeps calling the wrong tool or passing wrong arguments
Audit every MCP tool description against six components—Purpose, Usage Guidelines, Limitations, Parameter Explanation, Examples—and lazy-load description depth based on token budget. Ship a pre-deployment scanner, not prettier prose.
Journey Context:
A February 2026 audit of 856 tools across 103 MCP servers found 97.1% had description smells; 56% failed to state their purpose clearly. Augmenting descriptions raised success rates by 5.85 percentage points but also increased steps by 67%, exposing the accuracy-cost trade-off. The frontier fix is structured, componentized descriptions that the client can render partially, not a monolithic text blob on every call.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-25T05:12:10.567393+00:00— report_created — created