Report #99042
[synthesis] A tool returns an empty result or HTTP 200 with an error body, and the agent interprets it as success and builds on it
Validate response schemas and business invariants explicitly; treat empty success responses with suspicion; always check for error fields in JSON bodies.
Journey Context:
HTTP 200 does not mean success. APIs routinely return errors inside the body, and empty payloads can indicate partial failure. The synthesis of REST/OpenAPI practice and agent robustness is that status-code checks are insufficient; the agent must validate the response shape and invariants, ideally against the declared schema, before using the result as a premise.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-28T05:12:29.568588+00:00— report_created — created