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

Annotations already declare destructiveHint=true, so the description's real value is explaining the two-phase behavior — without confirm:true nothing changes and a preview is returned — which is not in any structured field. It does not state whether deletion is reversible or irretrievable, which is the one meaningful gap for a destructive operation.

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 short sentences, effect stated first and the confirm gating second. No filler, nothing truncated that matters.

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 simple two-parameter destructive tool with annotations covering the safety profile and no output schema, the description covers the action, its consequence, and the preview safeguard. Only irreversibility and recovery options are left unstated.

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 50%, and the one parameter the description touches (confirm) is already documented in the schema at length, so the description largely restates it. webhookId has no description anywhere, though its meaning is self-evident from the name. Baseline 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 ('Deletes one of the account's webhooks') and adds the consequence ('nothing more is sent to its address'), which makes the effect unambiguous. It doesn't explicitly contrast with siblings like update_webhook or test_webhook, but the verb+resource pairing is specific enough to select correctly.

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?

The description gives an operational rule (confirm: true required, otherwise preview) but never says when to prefer this over update_webhook to merely disable a webhook, nor when deletion is appropriate versus leaving it inactive. Usage is implied rather than contrasted with alternatives.

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