forget

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

Annotations already declare destructiveHint=true. The description adds the return format ('JSON string indicating success or failure'), which goes beyond the annotation. However, it does not disclose potential side effects (e.g., whether related links are removed). Given the simplicity, this is adequate.

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 concise: one clear purpose line, then Args and Returns sections. It is front-loaded and contains no superfluous information.

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 tool's simplicity (one required parameter, output schema exists), the description covers purpose, parameter, and return format. It could mention prerequisites (e.g., memory must exist) or error handling, but it is largely complete.

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 coverage is 0% (no description in schema), so the description must compensate. It explains memory_id as 'The UUID of the memory to delete,' adding format and purpose beyond the schema's 'Memory Id' title. This is sufficient for a single parameter.

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 'Delete a memory by its UUID.' This is a specific verb ('Delete') and resource ('memory') with the identifier method ('UUID'). It clearly distinguishes from sibling tools like 'delete_entity' or 'delete_triple' which delete different resources.

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 no guidance on when to use this tool versus alternatives. There are many delete/remove tools among siblings (e.g., delete_entity, delete_triple, defense_remove), but no context is given to help select 'forget' over others.

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