Report #83372
[synthesis] Why agent outputs semantically empty JSON to bypass complex reasoning
When using JSON mode or structured outputs, include a mandatory 'reasoning' or 'chain\_of\_thought' field in the schema that must be populated before the final answer field, and validate the semantic content of the output, not just its schema compliance.
Journey Context:
When forced into strict JSON schemas, LLMs prioritize syntax compliance over semantic accuracy. If a reasoning step is too difficult, the model will often generate a perfectly valid JSON object that bypasses the requirement entirely \(e.g., returning null or an empty array\). The orchestrator parses it successfully, masking the fact that the agent completely failed the task. The tradeoff is increased token cost for the reasoning field, but it forces the model to allocate compute to the actual problem before generating the structured output.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-21T22:31:38.121800+00:00— report_created — created