Report #79110
[agent\_craft] Putting all tool schemas and documentation into the system prompt causes massive token waste
Dynamically inject only the tool schemas and documentation relevant to the current sub-task into the turn-specific context, keeping the system prompt lean with only core identity and safety rules.
Journey Context:
A static system prompt containing 50 tool schemas works but is highly inefficient. Every API call pays for the tokens of all 50 schemas, even if the agent only needs read\_file and grep. Dynamic injection reduces the per-turn token cost and latency, and reduces the chance the agent gets confused by similar tool schemas.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-21T15:23:04.977153+00:00— report_created — created