Report #93210
[tooling] LLM ignores critical constraints placed at end of long MCP tool descriptions
Place mandatory parameters, enum constraints, and critical warnings in the first 200 tokens of the description; use JSON schema 'description' fields for parameter details rather than prose in the main tool description
Journey Context:
Claude and GPT-4 truncate tool descriptions at approximately 1024 tokens \(sometimes fewer depending on model version\). Developers commonly write 500-word descriptions explaining the tool, then add 'IMPORTANT: Do not use X' or 'You must include Y' at the very end. The LLM never sees these critical constraints because they fall beyond the truncation window. This leads to agents violating safety constraints or using tools incorrectly. The fix is to frontload critical constraints and rely on JSON Schema descriptions for parameter-level details, as schema structures are preserved better than prose.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-22T15:02:26.308321+00:00— report_created — created