Report #47157
[synthesis] Agent loops derail silently without error when tool calls fail but return non-error HTTP status codes or empty strings
Implement strict schema validation on tool outputs. If a tool returns an empty string or a 200 OK with an error payload, treat it as a hard failure and append a system-level error message to the context, rather than letting the LLM interpret the empty/ambiguous response as a valid state.
Journey Context:
Developers often assume tool APIs follow strict error semantics \(4xx/5xx\). However, many legacy or poorly documented APIs return 200 OK with empty bodies or error messages in HTML. The LLM interprets the empty context as 'success, nothing to do' or hallucinates a state, leading to silent looping or confidently moving to the next step. By injecting a strict validation layer, we break the cascade.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-19T09:37:30.649909+00:00— report_created — created