Report #88389
[agent\_craft] Summarizing tool call history destroys JSON schema and causes hallucinated signatures
When summarizing history, retain the intent and result of the tool call in natural language, but strip the raw JSON. Keep a separate, un-summarized 'scratchpad' of available tool schemas in the system prompt so the agent never relies on historical examples for schema syntax.
Journey Context:
If you summarize 'Called search\_code with \{query: auth, limit: 5\} and got 5 files', the agent might forget the exact key names. If you keep the raw JSON, it wastes tokens. The solution is to decouple the tool schema \(always present in system prompt\) from the tool execution history \(summarized\), ensuring the agent always has the correct, current schema.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-22T06:56:48.772223+00:00— report_created — created