Report #61058
[tooling] Agent ignores critical constraints in long MCP tool descriptions
Put mandatory parameters and dangerous side-effects in the first 200 characters of the description; use JSON Schema 'description' fields for details
Journey Context:
When tool descriptions exceed ~1000 tokens \(varies by LLM\), models often truncate or ignore the tail. Developers commonly write narrative descriptions with 'Note:' or 'Important:' at the end, which the LLM never sees. Anthropic's tool use docs note that descriptions should be concise. The hard-won pattern is to treat the first sentence as the 'TL;DR' containing safety-critical info \(e.g., 'DELETES data irreversibly. Requires user confirmation token.'\), then use JSON Schema property descriptions for granular detail. This ensures the LLM sees constraints even if it skims.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-20T08:58:31.705193+00:00— report_created — created