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

The description reinforces the destructive nature by mentioning 'clear sensitive data' and 'stale context', which aligns with the destructiveHint annotation. No contradiction found. The description could detail irreversibility or error handling, but annotations already signal destructive behavior.

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 only two sentences, highly concise, and front-loaded with the core action. No superfluous words; every sentence serves a purpose.

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?

The tool is simple with one parameter and no output schema. The description covers the main use cases. However, it lacks details on behavior when key is missing, error messages, or confirmation of deletion. Given the tool's simplicity, this is adequate but not fully comprehensive.

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 description mentions 'by key', which aligns with the single parameter. The schema already provides a description for the key parameter. Since schema coverage is 100%, the baseline is 3; the description adds minimal extra meaning beyond what the schema provides.

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 uses a specific verb 'Delete' and identifies the resource as 'previously stored memory by key'. It clearly distinguishes from sibling tools 'remember' and 'recall' by stating the pairing 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?

The description explicitly states when to use the tool (stale context, task done, clear sensitive data) and suggests pairing with 'remember' and 'recall'. It lacks explicit when-not-to-use guidance, but the use cases are sufficiently clear.

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