memory_delete_memory

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

With no annotations provided, the description carries the full burden. It discloses the irreversible nature of the action ('Permanently delete') and the prerequisite that the ID comes from a previous search result. It does not mention permissions or error behavior, but these are less critical for a simple one-parameter delete tool.

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, front-loaded with the action, and includes only essential information. No redundant wording; every phrase contributes to understanding the tool's purpose and usage.

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 parameter, no output schema), the description is complete. It specifies what the tool does, what input it needs, and how to obtain that input. It adequately covers all necessary context without over-explaining.

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 already provides 100% coverage for the single 'id' parameter with format and description. The description adds semantic value by clarifying that the ID originates from a previous memory search result, which is useful context not present in the schema.

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 explicitly states the action ('Permanently delete'), the resource ('a stored memory'), and the required identifier ('by its ID'). It clearly distinguishes this from sibling memory tools like memory_save_memory or memory_search_memory by specifying the delete operation.

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 gives a clear usage context by instructing to use the memory ID from a previous search result. This implies the tool is for deleting previously retrieved memories, but it does not explicitly name alternatives or exclusions such as memory_update_memory for modifying instead of deleting.

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