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

Annotations already declare destructiveHint=true and idempotentHint=false, but the description goes well beyond them: loss is permanent and irreversible, the pathName is freed immediately while contents are purged asynchronously in the background, protected lists with items are refused, and the call costs 1 request. This is unusually rich behavioral disclosure for a mutation tool.

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?

Five tight sentences, front-loaded with the destructive outcome, then the permanence/async behavior, then the refusal condition and confirmation directive. Every sentence carries distinct, load-bearing information with no filler.

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 destructive two-parameter tool with an output schema already covering return values, the description supplies everything an agent needs: irreversibility, immediate vs. background effects, the refusal edge case, and the user-confirmation requirement. No material gap remains.

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% with only two parameters, so the schema already documents that 'list' accepts an id or pathName and that 'confirm' must repeat the same value. The description adds a workflow note about confirming with the user but no additional parameter-level meaning, so the baseline of 3 is appropriate.

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 and resource ("Permanently delete a list") plus the cascade scope ("with all of its items and indexes"). It explicitly distinguishes itself from the item-level deletion path ("Unlike an item, a deleted list can't be restored"), so an agent can tell it apart from delete_item without opening either 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 a clear precondition ("A protected list that still has items is refused") and a procedural directive ("Confirm with the user first"), which is exactly the guidance needed before a destructive call. It implies the item-deletion alternative via the restore contrast but doesn't name a sibling tool explicitly, keeping it 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.