delete_memory

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

The description contradicts the annotations. Annotations indicate readOnlyHint=true (suggesting a read-only operation), but the description claims 'Delete memory' (a destructive write operation). This is a serious inconsistency that undermines behavioral transparency.

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 extremely concise with two short sentences that are front-loaded and waste no words. Every sentence serves a clear purpose: stating the action and providing usage context.

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 contradiction between annotations and description, the presence of an output schema (which might help), and the lack of parameter semantics, the description is incomplete. It fails to provide reliable information about the tool's behavior and parameters, making it inadequate for proper 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 schema description coverage is 0%, and the description provides no information about the 'memory_file_name' parameter beyond what the schema title indicates. It doesn't explain what this parameter represents or how to use it, failing to compensate for the low schema coverage.

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 the action ('Delete memory') which is a specific verb+resource, but it doesn't differentiate from sibling tools like 'edit_memory' or 'write_memory' beyond the basic action name. The purpose is clear but lacks sibling differentiation.

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 provides explicit context for when to use this tool: 'Only on explicit user request.' This gives clear guidance on usage conditions, though it doesn't specify alternatives or when not to use it beyond this constraint.

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