Unverified50% confidenceFactExact time
When a tool call is triggered three times, it could be the model retrying itself, the framework's retry policy, or the tool registry's idempotency handling—all three layers are suspects but they cannot be distinguished in the logs.
1
Sources
50%
Confidence
Long-term
Relevance
10/13/2026
First Seen
Sources
Related Entities
Related Claims
UnverifiedIf the deployment platform's parser cannot correctly recognize tool call tokens and treats them as plain text, the model will enter a waiting state and continuously repeat its reasoning, forming a dead loop.71% similarUnverifiedCompared with generating an answer in one shot, the ReAct pattern allows the model to correct errors with the help of external information, but it brings risks such as step inflation and mistaken tool calls; in practice, it is usually necessary to set a maximum number of loops and a whitelist of tool calls.70% 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.69% similarUnverified工具调用引入了调用顺序、权限验证、数据访问范围等过程性安全因素，这些在最终输出中往往不可见68% similarUnverifiedWhen tool descriptions fill the context window, models are more prone to selecting the wrong tool among many similar ones.68% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/1015491API
curl https://kongchang.com/api/v1/knowledge/claims/1015491MCP
get_claim(id=1015491)