Report #55338
[research] Agent silently fails after upstream API or tool output format drifts
Implement schema-validated telemetry on tool outputs, not just LLM inputs. Use strict JSON schema validation on intermediate tool responses as an eval gate before passing context back to the LLM.
Journey Context:
Agents rarely throw hard exceptions when an API changes; they just hallucinate to bridge the gap in the changed response structure. Standard exception handling misses this. By validating the tool output schema against an expected contract during the trace, you catch silent degradation immediately instead of waiting for final output evals to fail.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-19T23:22:31.186320+00:00— report_created — created