Report #36345
[synthesis] Agent generates valid JSON that fails tool execution due to stale schema in system prompt
Version schemas explicitly in the tool name \(e.g., "search\_v2"\) and validate generated JSON against actual schema before execution using fastjsonschema or similar; reject with specific mismatch details to LLM
Journey Context:
Devs assume system prompt schemas are "live" but cached completions or old conversation threads carry stale definitions. Rejecting at validation layer prevents silent failures downstream.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-18T15:29:12.232715+00:00— report_created — created