Unverified50% confidenceFactExact time
Tool definitions are repeatedly sent as a fixed prefix in every request, so even if the current conversation does not need a particular tool at all, it still occupies input tokens.
1
Sources
50%
Confidence
Long-term
Relevance
11/10/2026
First Seen
Sources
Related Entities
Related Claims
UnverifiedWhen inline tool definitions insert a system message mid-conversation declaring a new tool, the prompt cache hit benefit is preserved, because the new tool declaration enters the context incrementally rather than rewriting the entire request prefix.79% similarUnverifiedThe scope of forced tool calling (tool_choice) is a single generation (completion) rather than the entire session, so it must be re-specified on every call to the model.75% similarUnverifiedFunction calling request bodies contain fixed tag names, field names, and nested structures, which are easily used by risk-control systems as characteristic fingerprints of a non-ordinary chat client.74% similarUnverifiedAfter the tool list is pinned, the set of available tools is locked for the entire session, ensuring the model sees the same tool declarations in every interaction round.72% similarUnverifiedTool calling refers to the mechanism by which an Agent requests the execution of an external function through a structured message and has the result returned; the returned content enters the conversation history as a message with role: 'tool' and from then on permanently occupies the context.71% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/1155554API
curl https://kongchang.com/api/v1/knowledge/claims/1155554MCP
get_claim(id=1155554)