Why agents need context governance beyond bigger windows
模型的窗口不是无限大的垃圾桶:为什么智能体需要上下文治理
More tools mean more noise in the context window. Anthropic's MCP sandbox cuts 150K tokens of tool definitions down to ~2K of high-signal input. Google ADK splits agent state into working context, session state, long-term memory, and file artifacts—intermediate outputs stay off-prompt by default. Manus reports a ~100:1 input-to-output token ratio in production; they keep raw files in a sandbox, stabilize tool-call formats for KV cache hits, and rewrite a todo.md at the window's end to fight lost-in-the-middle. Headroom compresses JSON and logs by 60–95%, but lacks large-scale validation on hard coding tasks. The takeaway: RAG is the foundation, but the real engineering is runtime information governance.
Why it matters: Anthropic shrinks tool definitions inside a sandbox, while Google ADK isolates intermediate artifacts by state layer to cut agent context usage.