delete_memory

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

The description notes the action is 'permanent,' which is a key behavioral trait. However, no annotations are provided, and the description lacks details on side effects, permissions, or confirmation steps.

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?

Two concise sentences deliver the essential information without redundancy. The description is front-loaded and efficiently communicates the tool's purpose and a key implication (permanence).

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 no output schema, the description covers the core action and consequence. However, it could better contextualize usage among siblings like consolidate_memories or save_memory.

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 single parameter memory_id is fully described in the schema with 'Memory ID to delete.' The description adds no extra semantics beyond the schema, which already covers 100% of parameters.

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 'Delete a specific memory by its ID. This is permanent.' clearly states the action (delete), the resource (memory), and the method (by ID). It is distinct from siblings like bulk_delete or update_memory.

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 explicit when-to-use or when-not-to-use guidance is given. The purpose implies it is for deleting a single memory, but alternatives like bulk_delete or update_memory are not mentioned.

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