context

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description bears the full burden of disclosing behavior. It mentions detecting expiry and handling reset, but does not clarify whether reset is destructive, what optimize does, or if there are side effects. This is a significant gap for a tool that appears to mutate state.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single short sentence with no redundancy, yet it is more of a label than a complete explanation. It is concise in length but lacks substance, conveying only a vague sense of functionality without concretely stating what the tool does.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given no annotations, no output schema, and an action enum with non-obvious values (check, reset, optimize), the description is incomplete for correct invocation. It does not explain what each action does, how tokenCount and maxTokens interact, or what the expected result of calling the tool is.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the schema already documents all parameters with descriptions. The tool description adds no parameter-level detail beyond the schema, so the baseline of 3 applies. It neither enhances nor conflicts with schema semantics.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific function ('管理Context状态，检测过期并处理重置') with clear intent, and distinguishes itself from siblings like log_conversation and files by focusing on context state management. However, '管理' is somewhat generic, and the specific operations (check/reset/optimize) are not elaborated.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is given on when to use this tool versus sibling tools such as log_conversation or tasks. The description only states what the tool does, not in which situations it should be invoked, nor any exclusions to avoid incorrect usage.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.