Unverified50% confidenceTradeoffExact time
The traditional agentic workflow approach is to declare all available tools at once during session initialization, keeping the tool set fixed throughout the conversation, which causes the context window to be heavily occupied by tool descriptions when the number of tools is large.
1
Sources
50%
Confidence
Long-term
Relevance
9/24/2026
First Seen
Sources
Related Entities
Related Claims
UnverifiedA single Agentic session may span dozens of operational steps involving multiple files and modules, significantly amplifying the problem of fragmented work records.79% similarUnverifiedAgent框架慢于直接对话主要因为注入大量系统提示词工具定义、ReAct多轮推理和上下文累积导致输入token数增长78% similarUnverifiedAgentExecutor每次工具调用前会重新拼接完整对话历史进Prompt，导致Token消耗随任务步骤线性增长77% similarUnverifiedIn agent or tool-calling scenarios, invisible content such as system prompts, tool definitions, and retrieved documents consumes a large number of tokens.76% similarUnverifiedCompared to single-turn dialogue, Agent systems introduce three additional dimensions: memory, tool invocation, and planning.76% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/946269API
curl https://kongchang.com/api/v1/knowledge/claims/946269MCP
get_claim(id=946269)