delete_memory

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

States 'This performs a soft delete,' which is key behavioral info, but no other details on reversibility, permissions, or side effects. With no annotations, the description carries full burden but is minimal.

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?

Compact three sentences plus a bullet list, no redundant text. Front-loaded with purpose and usage context, well-organized parameter details.

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?

Covers purpose, usage, behavioral detail, and parameters. Output schema exists, so missing return value info is acceptable. Lacks error conditions or idempotency, but adequate for a simple delete.

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 description must compensate. It adds meaning by explaining defaults and optional filters (user_id, group_id, memory_type), but lacks examples or allowed values, leaving gaps.

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 'Delete memories from EverMemOS' with a specific verb and resource. It distinguishes from siblings like get_memories, search_memory, and store_memory by being the only delete operation.

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?

Explicitly says 'Use this tool when the user explicitly asks to forget or remove certain memories.' Provides clear context, though lacks explicit 'when not to use' or alternative recommendations.

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