Report #95452
[synthesis] Agent silently derails because tool returns empty/default success on malformed input instead of throwing a validation error
Enforce strict JSON schema validation on tool inputs at the orchestration layer; if a tool call doesn't match the exact schema, reject it and return a structured error before the tool executes.
Journey Context:
APIs often default missing fields rather than failing, returning 200 OK with an empty state. LLMs frequently omit optional or even required nested fields in JSON arguments. If the tool executes and returns a generic success, the agent assumes the state is updated and moves on, leaving the system broken. Pre-execution schema validation forces the agent to self-correct its syntax before state corruption occurs.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-22T18:47:34.551490+00:00— report_created — created