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

Annotations already declare destructiveHint=true, readOnlyHint=false, and non-idempotency, so the safety profile is covered. The description adds genuinely useful behavior the annotations don't: that the call defaults to a preview/dry run and should only be executed for real after explicit user confirmation, which is critical for a destructive bulk operation. It does not address re-invocation/idempotency behavior, leaving a small 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?

Two tight sentences with no filler. The destructive scope is front-loaded, followed immediately by the safety default and the confirmation gate, which is the right ordering for a destructive tool.

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?

An output schema exists, so return values need no explanation. Given the tool is a simple three-parameter bulk delete, the description covers everything an agent needs: valid identifier source, deletion scope, dry-run default, and the confirmation requirement before real deletion.

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 coverage is 100%, so entity_type and entity_id are already documented and the baseline is 3. The description adds value by reinforcing the dry_run semantics with a workflow rationale ('pass dry_run=false to delete after the user confirms') and by tying entity_id to list_entities output, which clarifies the dependency beyond the raw field description.

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 precise verb+resource+scope: 'Delete every memory belonging to one entity returned by list_entities.' This scope language cleanly separates it from delete_memory (one memory) and delete_all_memories (everything), even without naming them, and the 'cursor' source example makes the entity concept concrete.

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?

It establishes the workflow context by pointing back to list_entities as the source of valid entity identifiers, and it states the safe default (dry run) plus the condition for real deletion after user confirmation. It does not explicitly contrast against delete_memory or delete_all_memories, so it stops short of a full when-to-use-one-vs-alternative statement.

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