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

Annotations already include destructiveHint=true and idempotentHint=true, so the description need not repeat those. It adds context that the memory must be 'previously stored' and that the tool is for clearing 'sensitive data', which goes beyond the structured fields. It does not describe behavior for missing keys, but the idempotentHint covers repeatability.

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 three concise sentences, front-loaded with the core action ('Delete a previously stored memory by key') and then usage guidance. No fluff or redundancy; every sentence earns its place.

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?

For a simple one-parameter tool with full schema coverage and annotations for destructiveness and idempotency, the description provides sufficient context: it explains when to use the tool, names related tools, and handles the key semantics. No output schema is needed for such a simple deletion operation.

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 covers the only parameter 'key' with full description ('Memory key to delete') and an example. The description adds no additional parameter semantics, but the schema already provides complete information, so baseline 3 is appropriate.

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 clearly states the tool deletes a previously stored memory by key, using a specific verb and resource. It distinguishes from sibling tools like 'remember' (store) and 'recall' (retrieve) by explicitly naming them in the context.

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?

Provides explicit usage conditions: use when context is stale, task is done, or clearing sensitive data. It names the siblings 'remember' and 'recall' and tells the agent to pair with them, effectively distinguishing when to use this tool versus the alternatives.

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