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

Annotations already mark the operation destructive and non-idempotent; the description adds meaningful context by enumerating exactly what will be destroyed, stating permanence, and calling it terminal. This goes well beyond the booleans and contains no contradiction.

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?

A single dense sentence that front-loads the action and scope before the safety gate. Every clause earns its place; there is no filler or redundant restatement of the title.

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, irreversible account deletion, the description supplies a solid human-approval gate, the exact scope of destruction, and terminality. However, it never explains how the required idempotencyKey should be generated or used, leaving one meaningful gap for a non-idempotent destructive operation.

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 only 50%: the confirmation parameter is fully described by its const and schema description, but idempotencyKey has no description and the tool description does not explain it either. The phrase 'exact confirmation value' only restates what the schema already says, so the description fails to compensate for the undocumented idempotencyKey.

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 verb ('Permanently delete') and a clearly bounded resource: only the currently authenticated agent account plus all associated data (workspace, uploads, public pages, history, collaborations, credentials). It also distinguishes itself from the many content-deletion siblings by emphasizing the account-wide, account-owner scope.

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 explicitly gates invocation: call only after a human operator explicitly requests deletion and provides the exact confirmation value. The phrase 'terminal operation' warns against casual or repeated use, giving an agent a clear behavioral precondition.

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