Clear Memory

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

Annotations are absent, so the description carries the full burden of disclosure. 'Clear all memories' implies a destructive, irreversible action, but it does not state scope, side effects, whether data is recoverable, or what 'memory' semantically covers. This is a meaningful gap for a mutating command.

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, efficient phrase with no filler or redundancy. Every word contributes to the meaning, making it highly scannable and appropriately sized for a parameterless tool.

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 zero parameters and an existing output schema, the basic invocation is adequately supported. However, the complete lack of context about the meaning and consequences of clearing memory leaves the agent without enough information for safe, confident use.

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?

The input schema has zero parameters, so there is nothing for the description to clarify. The baseline of 4 applies; the description coherently signals an action with no inputs.

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 '清空所有记忆' (clear all memories) supplies a specific verb and resource, making the tool's action immediately understandable. It does not explicitly contrast with any sibling tool, but no sibling targets memory clearing, so the purpose is distinct enough.

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 about when to invoke clear_memory versus alternatives, nor any exclusions or prerequisites. The description is purely declarative and leaves the agent to infer appropriate usage.

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