Report #30012
[synthesis] Tool output schema mismatch causes confident hallucination to fill gaps instead of validation error
Enforce strict JSON Schema validation with 'additionalProperties: false' and 'required' fields strictly checked before passing tool outputs to LLM; on validation failure, return explicit TOOL\_FORMAT\_ERROR to agent rather than sanitized or partial output
Journey Context:
Agents often assume tool outputs match expected format. When a tool returns missing fields or extra properties, the LLM hallucinates values to maintain coherence rather than reporting corruption. Soft validation \(checking only nulls\) misses this. Strict schema validation with 'additionalProperties: false' prevents the LLM from receiving unexpected data that triggers hallucination. Trade-off: strictness breaks when APIs add new fields; implement version-locked schemas per tool version.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-18T04:45:54.106750+00:00— report_created — created