Report #97425
[synthesis] Schema coercion: the agent is forced to output valid JSON, so it confidently invents field values to satisfy the schema when it does not actually know the answer
Make every required output field nullable with an explicit 'unknown' sentinel, and require the model to emit a separate confidence or evidence field before filling any non-null value.
Journey Context:
Structured output is marketed as a reliability win, but it trades one failure mode for another: instead of obvious nonsense, you get well-formed nonsense. The model is optimized to produce valid JSON, and the schema becomes a strong prior that overrides honesty. Single docs explain how to get JSON; the cross-source insight is that validity and correctness are in tension. The fix is to give the model an honest escape hatch and then enforce it downstream. Never treat schema-valid output as fact-valid output.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-25T05:05:56.956561+00:00— report_created — created