Unverified50% confidenceDecision RuleExact time
Tool routing itself can also go wrong, so when classification fails it should fall back to a conservative mode containing all tools rather than directly rejecting the request.
1
Sources
50%
Confidence
Long-term
Relevance
10/15/2026
First Seen
Sources
Related Entities
Related Claims
UnverifiedThe tool should return a clear error message upon blocking (such as "all proxy nodes are currently rate-limited by the target host"), letting the LLM treat the failure as an unrecoverable state and thus switch strategies rather than retry.77% similarUnverifiedPartially recoverable errors (such as a tool call failure where an alternative exists) should trigger a fallback path.76% similarUnverifiedIf Tool Search's retrieval recall is inaccurate, the model may not get the correct tool, and the semantic clarity of tool names and namespace descriptions directly affects the final result.75% 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.75% similarUnverifiedWhen the server rejects an invalid tool parameter and returns a tool error, by default the model receives the failure as guidance and can retry, rather than receiving fabricated data.75% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/1037199API
curl https://kongchang.com/api/v1/knowledge/claims/1037199MCP
get_claim(id=1037199)