Report #58467
[synthesis] Tool schema mismatch triggers hallucinated field mapping
Enable strict mode for all function calling schemas and validate returned payloads against the schema before consumption; reject 200 OK responses that violate the contract.
Journey Context:
When tools return 200 OK with unexpected schemas \(extra fields, type mismatches\), LLMs do not error but hallucinate 'mappings' between received and expected fields to maintain conversational coherence. This creates 'zombie data' where downstream steps reference hallucinated keys. Non-strict mode allows this; strict mode would force an error catch. The alternative of manual parsing loses flexibility. The fix enforces contract adherence over graceful degradation.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-20T04:37:27.071134+00:00— report_created — created