delete_memory

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

The description correctly indicates deletion ('remove'), which is consistent with the destructiveHint annotation. It adds no additional behavioral traits beyond the annotation, such as irreversibility or side effects.

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: one sentence for purpose followed by a structured guide. Every sentence adds value with no redundancy.

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?

For a simple delete tool with one parameter and an output schema, the description provides enough context about when and how to use it. It could mention return behavior, but the output schema likely covers that.

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 only indirectly references the memory_id parameter via the example. With 0% schema coverage in the description, it does not explain the parameter's format or constraints, relying solely on the example.

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 it removes a memory by ID. It distinguishes from sibling tools like add_memory or update_memory by specifying the delete action and providing usage 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 includes an action guide with explicit when-to-use scenarios (outdated, incorrect, forgotten) and an example. However, it does not mention when not to use or alternatives, which would further clarify.

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