agent_memory_delete

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

Annotations already declare destructive and idempotent hints. The description adds value by specifying that a single entry is deleted and by disclosing the return format (JSON with 'success', 'key', and 'deleted' bool), providing more behavioral context than the annotations alone.

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 highly concise and well-structured: one clear purpose sentence followed by an Args/Returns breakdown. Every sentence contributes essential information, with no redundancy or filler.

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 single-parameter destructive tool, the description is nearly complete: it states the action, the parameter, and the return format. The destructive hint in annotations covers the safety profile. It could be slightly more explicit about behavior on missing keys, but the 'deleted' bool in the return implies this.

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 covers the sole parameter 'key' with a description identical to that in the tool description (100% coverage). The description adds no new information about the parameter beyond what the schema already provides, so the baseline of 3 applies.

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 starts with 'Delete a single memory entry by key', which is a specific verb+resource pair that clearly distinguishes this from siblings like save, load, list, and search. It unambiguously states the tool's function.

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 implies when to use this tool (to delete a specific memory entry) but provides no explicit guidance on when to choose this over alternatives, nor any exclusions or prerequisites. Usage is inferred from the verb and resource.

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