Unverified50% confidenceFactExact time
The 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.
1
Sources
50%
Confidence
Long-term
Relevance
10/15/2026
First Seen
Sources
Related Entities
Related Claims
UnverifiedTool outputs are repeatedly read and repeatedly billed in every subsequent round of conversation until the context is compressed.79% 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.78% similarUnverifiedThe platform measures usage by token consumption rather than conversation turns; the longer the prompt, the more context, and the larger the model, the faster tokens are consumed.75% similarUnverifiedA single Tab completion in Cursor may consume thousands of input tokens for context construction, whereas a pure conversation scenario does not incur this hidden cost74% similarVerifiedLong conversations package and resend the entire context history to the model, which is counted toward the token usage of each request; the longer the conversation, the more tokens a single request consumes.73% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/1033230API
curl https://kongchang.com/api/v1/knowledge/claims/1033230MCP
get_claim(id=1033230)