Unverified50% confidenceOpinionExact time
Before modifying the Prompt again, first read several complete records of Agent failures; usually you will find the root cause lies in tool design (misreading tools, being flooded by output, repeatedly retrying on errors it cannot understand), rather than in the Prompt itself.
1
Sources
50%
Confidence
Long-term
Relevance
10/16/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.77% similarUnverifiedFailure records in OpenAmer's ledger include a why field that categorizes failure reasons into human-readable information, such as task timeout, tool returning an unexpected data structure, path not reaching the objective, missing dependencies, etc.74% similarUnverifiedFailure modes describe the reproducible ways a tool fails under specific inputs.73% similarUnverifiedWhen a tool returns an error or empty output, it should be rejected immediately rather than passing on incomplete data — this is a fail-fast handling approach73% similarUnverifiedTool error messages should be returned to the model as ordinary tool results, containing a plain-language explanation of the problem and what to do, and 'Do not retry' can stop the model from repeatedly retrying hopeless calls.73% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/1044250API
curl https://kongchang.com/api/v1/knowledge/claims/1044250MCP
get_claim(id=1044250)