delete_memory

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

No annotations are provided, so the description carries the full behavioral burden. It says 'Delete' and 'Returns: JSON result,' but does not disclose destructive/irreversible implications, permission requirements, or side effects. 'Returns: JSON result' is also redundant because an output schema exists.

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 short and front-loaded with the operation and parameter. The Args/Returns structure is easy to scan, though the 'Returns: JSON result' line is unnecessary given the output schema.

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 destructive single-parameter operation with no annotations and an output schema, the description covers only the bare invocation. It lacks the safety and behavioral context an agent needs before calling a delete tool.

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 description coverage is 0%, so the description must compensate for the undocumented entry_id parameter. It only restates 'Memory entry id' in tautological fashion, adding no format, sourcing, or validation details beyond the schema's parameter name.

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 gives a specific verb and resource: 'Delete a memory entry by id.' This clearly distinguishes deletion from sibling memory tools such as save_memory, get_memory, search_memory, and cleanup_memory. It does not explicitly differentiate from cleanup_memory, but the core purpose is clear.

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 states what the tool does but gives no guidance on when to use it versus alternatives like cleanup_memory. It also omits prerequisites such as whether deletion is permanent or what happens if the entry_id does not exist.

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