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

The description confirms the destructive nature ('delete', 'clear'), aligning with annotations (destructiveHint=true). It adds context about why deletion is appropriate (stale data, security) beyond what annotations provide, though it could mention reversibility or scope.

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 two sentences: first sentence states the core action, second provides usage guidance and companions. It is efficient, front-loaded, and contains no unnecessary words.

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 the simple nature of the tool (1 param, no output schema), the description sufficiently covers purpose and usage. It could be improved by noting behavior for missing keys or idempotency, but overall is adequate.

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?

With 100% schema coverage and a single parameter, the description does not add new semantics beyond the schema's 'Memory key to delete'. Baseline of 3 is appropriate as schema already documents the parameter adequately.

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 action ('Delete') and the resource ('a previously stored memory by key'), directly matching the tool's name and title. It distinguishes from siblings by referencing 'remember' and 'recall', implying complementary roles.

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?

The description explicitly specifies when to use the tool ('context is stale, task is done, clear sensitive data') and suggests pairing with related tools ('remember', 'recall'), providing clear context and alternatives.

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