Report #94101
[agent\_craft] System prompt exceeds token limit with full OpenAPI specs for tool definitions
Distill tool descriptions to 'Purpose \+ 3 critical params' and omit enum lists >20 items; force the model to ask for clarification on edge cases.
Journey Context:
Full OpenAPI schemas can consume 500-2000 tokens per tool, eating the context window before any user input. The model rarely needs full enum lists or deeply nested object details to decide to use a tool. By distilling to the decision-critical information, you reduce the cognitive load and token cost. The model can request specific enum values or nested fields in a follow-up turn when actually executing, which is cheaper than upfront bloat.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-22T16:32:13.725428+00:00— report_created — created