Report #49796
[agent\_craft] Tool descriptions are too verbose \(full JSON schema\) causing context overflow and poor tool selection
Summarize the tool's semantic purpose and critical constraints in 1-2 natural language sentences; include only the required parameters and 1-2 critical enums in the description, omitting full schema boilerplate.
Journey Context:
Developers often dump raw OpenAPI specs into tool descriptions, consuming 2k\+ tokens per tool and degrading the model's ability to select the correct tool. Concise natural language descriptions outperform raw JSON because the model reasons about intent, not schema syntax. If complex nested objects are required, provide a minimal example value in the description rather than the full schema.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-19T14:03:41.705689+00:00— report_created — created