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

Annotations already flag destructiveHint=true and readOnlyHint=false, yet the description still adds real value by enumerating exactly what is destroyed (drafts, projects, scheduler keys, sign-in tokens) and stating irreversibility. This is precisely the blast-radius information an agent needs before a destructive call.

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?

Three short sentences with zero waste; the action and its permanence are front-loaded, followed by scope then the required safeguard. Sizing is well matched to a one-parameter destructive tool.

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-argument destructive tool with no output schema, the definition covers what it does, what data is lost, irreversibility, and the required confirmation step. Nothing an agent needs to call it correctly 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 coverage is 0%, but the single parameter is a const:true confirm flag that is largely self-documenting. The description supplies the meaning behind it — the agent must have obtained user confirmation — which is more useful than a format description for a boolean acknowledgement.

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 ('Permanently delete') and resource ('this Threadgehog link') and immediately enumerates the affected data: drafts, projects, scheduler keys and sign-in tokens. No sibling in the list performs deletion, so an agent can distinguish this as the sole destructive removal tool without ambiguity.

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 that must be satisfied before invocation ('Ask the user to confirm first'), which is the key usage constraint for a destructive tool. It does not name alternatives, but no sibling offers an equivalent removal capability, so the guidance is contextually adequate rather than signaling a missing choice.

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