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

Annotations already declare destructiveHint=true, readOnlyHint=false and idempotentHint=true, so the safety profile is largely covered. The description adds two things annotations cannot express: irreversibility ('It cannot be undone') and the ordering requirement to pass confirm only post-confirmation.

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 sentences, zero filler. The destructive scope is front-loaded, followed by the gating and confirmation rules in the same order an agent would apply them.

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 single-parameter destructive tool with no output schema and full annotation coverage, the description supplies everything an agent needs: what is deleted, when it is allowed, the confirmation gate, and irreversibility.

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?

There is 1 parameter at 100% schema description coverage, so the schema already documents confirm fully; the description's confirm guidance largely restates it. Baseline 3 is appropriate when the schema does the heavy lifting.

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?

States a specific verb (delete) and a precisely enumerated resource scope (searches, skill loads, ratings, issue reports) scoped to 'this user'. An agent can distinguish this from siblings like my_activity or feedback without opening any schema.

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?

Gives an explicit gating condition ('Use only when the user asks to delete their Edge data') and a sequencing rule for confirm, which is real when-to-use guidance. It stops short of naming a sibling alternative (e.g., deleting individual items), so 5 is not warranted.

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