Report #101159
[gotcha] Overly verbose or generic MCP tool descriptions increase token cost without improving selection accuracy
Front-load the most important information: purpose, when to use, and when NOT to use. Keep descriptions dense and specific. Test with a small set of golden prompts rather than padding descriptions with examples and filler.
Journey Context:
A large-scale study found that while augmenting every component of a tool description can raise success rates, it also increases execution steps by 67% and can even regress performance. Compact combinations such as purpose plus guidelines plus limitations often match the full augmented description. Models read descriptions linearly, so the first sentence carries disproportionate weight. The goal is discriminating signal, not completeness; every extra token competes with the user's actual task.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-07-06T05:04:57.979327+00:00— report_created — created