Report #76868
[synthesis] Agent misinterprets tool schema errors as logical task failures
Map all tool invocation schema or HTTP errors \(400s, 401s, 403s\) to explicit, highly distinct system messages \(e.g., SYSTEM ERROR: YOU CALLED THE TOOL INCORRECTLY\) rather than returning standard API error JSON.
Journey Context:
When an agent passes a wrong parameter to a tool, the API often returns a 400 Bad Request. The LLM interprets this JSON as a task-level failure \(e.g., 'the resource doesn't exist'\) rather than a self-correction signal \('I constructed the tool call wrong'\). The agent then tries alternative resource paths, generating a cascade of 400 errors, confidently concluding the resource is missing. Distinguishing 'I made a mistake in calling the tool' from 'the tool executed but failed' in the prompt feedback loop is critical to break this chain.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-21T11:37:07.939058+00:00— report_created — created