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

Annotations already declare destructiveHint=true and idempotentHint=true, so the core safety profile is structured data. The description adds genuine domain context beyond that – 'Permanently' and 'Pending deliveries are dropped' – which tells the agent about in-flight data loss that annotations cannot express. It stops short of stating error behavior for a nonexistent ID or that the webhook stops firing immediately.

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 with the destructive action front-loaded and the consequence tucked behind it; nothing is wasted. It is arguably a touch terse for a destructive operation, but efficient.

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 full annotation coverage, the description supplies the one fact annotations omit: pending deliveries are lost. Combined with the 100%-covered schema and destructive/idempotent hints, an agent has enough to call it correctly, though a note on failure mode for an unknown ID would round it out.

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 'id' documented as 'Webhook ID (wh_xxx).' including the expected format. The description adds no parameter-level detail, so the baseline 3 applies.

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+resource ('Permanently delete a webhook') that clearly distinguishes it from get-webhook, update-webhook, and the many other delete-* siblings by naming the resource. It does not, however, contrast it against a sibling such as update-webhook for reversible disabling, so differentiation is by noun rather than explicit text.

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?

There is no guidance on when to use this versus update-webhook (disable) or the retry-webhook-request siblings, and no mention of prerequisites or irreversibility checks. The agent must infer that this is the terminal teardown option.

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