Report #55262
[synthesis] Agent is misdirected into taking incorrect actions because a tool returns a successful but misleading response \(e.g., an API returns a default/empty object instead of a 404\)
Design tool schemas to require explicit status indicators and fail loudly on empty or null states, rather than returning successful empty data.
Journey Context:
LLMs are highly susceptible to treating any tool output as meaningful signal. If an agent queries a database for a user and the DB returns an empty array with a 200 OK, the agent might interpret this as the user exists but has no data and proceed to update the empty object, rather than realizing the user doesn't exist. This leads to a chain of confidently wrong actions based on a false premise. The fix isn't just better prompting; it's changing the tool interface. Tools must be designed for agentic use by converting empty successes into explicit errors or highly structured responses that force the agent to acknowledge the null state.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-19T23:15:00.664848+00:00— report_created — created