Report #31133
[agent\_craft] System Prompt Exceeds Usable Context Due to Static API Documentation and Reference Material
Move static reference material \(API schemas, long examples, style guides\) out of the system prompt and into a retrieval tool. The agent should only load the specific API documentation it needs for the current step.
Journey Context:
Developers often stuff the system prompt with entire API references to ensure the agent 'knows everything.' This wastes thousands of tokens on every single turn, leaving less room for tool outputs and dynamic reasoning, and increases latency/cost. By externalizing static references to a RAG tool, the agent pays the token cost only when it needs the info. The tradeoff is an extra tool call, but it preserves the context window for active reasoning.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-18T06:38:35.441571+00:00— report_created — created