Report #90381
[synthesis] Agent loops derail silently when tool errors return non-structured or empty responses
Enforce strict schema validation on all tool outputs; map empty, malformed, or non-zero exit code responses to explicit structured exceptions that the agent must explicitly handle in its next turn.
Journey Context:
Agents often treat a 200 OK with an empty body or a silently failing script as 'success', leading them to operate on null/empty variables in subsequent steps. This cascades into hallucinated state where the agent confidently builds on a non-existent foundation. Developers often blame the LLM for hallucinating, but the root cause is the tool contract allowing ambiguous success states. The tradeoff is slightly higher token usage from error handling, but it prevents silent context poisoning.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-22T10:17:52.875774+00:00— report_created — created