memory_delete

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

No annotations are provided, so the description carries the full burden. It states the tool 'removes' an entry, implying a destructive mutation, but does not disclose whether the operation is permanent, whether it errors on missing keys, or what the response contains. For a mutation with no annotation coverage, this is a significant gap.

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, with a one-sentence purpose and a clear, front-loaded parameter list. No fluff or redundant information; every line adds value. This is an optimally structured short definition.

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?

Although an output schema exists (not shown), the description omits critical context for a destructive operation: it does not mention side effects (e.g., irreversible deletion), error behavior on missing keys, or any confirmation/return message. For a delete tool with no annotations, an agent needs more than the bare action and parameter list to call it safely and correctly.

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 input schema has 0% description coverage, so the description must explain each parameter. It does: 'key' is the memory key to remove, 'project_root' is the required absolute path, and 'namespace' indicates a logical namespace with a default. This adds meaning beyond the bare schema titles and is sufficient for an agent to understand parameter purposes, though it could be more detailed (e.g., allowed formats).

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 a clear verb ('removes') and resource ('specific memory entry'), which unambiguously defines the operation. It is distinct from siblings like memory_store or memory_retrieve by the action. However, it does not explicitly differentiate from similar delete-like operations, though none exist among siblings, so it is clear enough.

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?

No guidance is provided on when to use this tool versus alternatives. The description only lists parameters and the core action, with no mention of contexts in which deletion is appropriate, prerequisites, or scenarios where another tool (e.g., memory_update_last) might be preferred. The agent must infer usage from the name alone.

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