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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so "Behavior: read-only" is largely redundant. The valuable addition is the irreversibility note ("content is gone", "never content"), but the wallet/nonce/signature auth flow — the real behavioral gotcha for calling this — is left entirely to the schema.

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 core information is front-loaded, but the second sentence restates the first almost verbatim ('audit log of deletions (ids, times, reasons, never content)'), which is wasted space in a three-sentence description. The exclusion clause earns its place; the duplication does not.

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 read-only, non-destructive query with no output schema, the description tells the agent what fields come back and that content cannot be recovered, which is enough to call it correctly. Only the memory_prepare prerequisite chain is unmentioned in prose, though the schema covers it.

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 100% and all four parameters (wallet, timestamp, nonce, signature) are documented in the schema itself, including the dependency on memory_prepare. The description adds no parameter-level meaning, which is acceptable given the schema baseline of 3.

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 names a specific resource (a deletion audit log) and enumerates its contents (ids, times, reasons, never content), so the agent knows exactly what this returns. It stops short of differentiating itself from the closely named sibling memory_history or from memory_delete, which leaves room for confusion among the memory_* family.

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?

"Use when you want your audit log of deletions" gives an explicit trigger, and "Not for recovering content, which is gone" gives an explicit exclusion plus the reason. It does not name sibling alternatives (e.g., memory_history for non-deletion events), so it falls just short of a 5.

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