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

Annotations already declare destructiveHint=true, idempotentHint=true and readOnlyHint=false, so the safety profile is covered; the description adds the important nuance that ids not owned by the authenticated user are silently ignored rather than erroring, plus the ordering rule (write the new memory, then delete the old). It does not describe the response body, though with no output schema that gap is minor for a single-argument delete.

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 destructive nature and the two trigger conditions are front-loaded, and the example is short and illustrative. It loses a point for restating the memoryId provenance rule that the schema already states verbatim, a small redundancy in an otherwise tight definition.

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 one-parameter destructive tool with full annotation coverage and no output schema, the definition supplies everything an agent needs: when to call it, when the correction workflow applies, where the id comes from, and what happens on foreign ids. No meaningful decision input is missing.

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 the single parameter already documents provenance (the `id` field from search_memory) and the silent-ignore ownership check, so the schema carries the load. The description's reminder to obtain memoryId from a prior search result restates that rather than adding new syntax or format constraints; baseline 3 applies.

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 very first sentence gives a specific verb and resource ("Permanently delete a memory about the user") and the word "permanently" immediately sets it apart from a soft-archive alternative. The body further distinguishes it from search_memory and from credential/file/strategy deletion siblings by scoping it to user facts.

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 names two explicit triggering conditions — an explicit user request to forget, and a correction flow where the old fact must be removed after the new one is written — and gives a concrete worked example (Tradier → IBKR). It also states the prerequisite that memoryId must come from a prior search_memory result, leaving nothing to infer.

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