Unverified50% confidenceFactExact time
Silent changes to external APIs (such as changing default values, field meanings, or response behavior) may cause an Agent to continue working on wrong assumptions, even when tool calls return 200 and schema validation passes.
1
Sources
50%
Confidence
Long-term
Relevance
10/27/2026
First Seen
Sources
Related Entities
Related Claims
UnverifiedAfter reading the error message returned by a tool, the Agent will decide its next action based on it, and a bare error (such as {"error": "not found"}) will cause the Agent to repeat the same call or make up an answer on its own.78% similarUnverifiedWhen an API returns an error, graceful degradation should be implemented—providing friendly error messages, cached fallback results, or a temporary switch to basic functionality—rather than crashing outright.73% similarUnverifiedWhen a tool calling an external API throws an error, the designer must decide whether to pass the error to the model for a retry or to raise it directly to the user73% similarUnverifiedIn Agentic scenarios, sources of error may include prompt design flaws, tool API return formats not matching expectations, information loss during multi-step reasoning, or gaps in the model's domain knowledge.72% similarUnverifiedHow tools are described and the format of error messages directly affect whether an agent can correctly call tools and recover from failures.72% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/1105193API
curl https://kongchang.com/api/v1/knowledge/claims/1105193MCP
get_claim(id=1105193)