Unverified50% confidenceFactExact time
When 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.
1
Sources
50%
Confidence
Medium-term (~90 days)
Relevance
10/18/2026
First Seen
Valid until: 1/16/2027
Sources
Related Entities
Related Claims
UnverifiedInline tool definitions turn tool registration from request-level configuration into a conversation-level event, making context budget management more fine-grained and allowing tool permissions to be tightened or relaxed as the conversation stage changes.78% similarUnverifiedDuring multi-turn tool calls, each tool execution result is appended to the conversation history as a new tool_result message, and the model reads the outputs of previous steps from the conversation context rather than retaining intermediate values in internal memory.77% similarUnverifiedInline tool definitions re-declare tools via a system message, with the effect of overriding or extending the set of tools currently available to the model.77% 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.77% similarUnverifiedThe observation returned by any tool call permanently resides in the conversation context as tokens, and is re-read and billed in every subsequent round, so the more verbose the tool output, the higher its marginal cost.72% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/1057632API
curl https://kongchang.com/api/v1/knowledge/claims/1057632MCP
get_claim(id=1057632)