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

Annotations already declare destructiveHint=true and idempotentHint=true, so the safety profile is carried by structured data. The description adds only the practical consequence (deliveries stop), and is silent on whether the endpoint configuration and its delivery history are permanently lost, whether the call is reversible, or what auth scopes are needed.

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?

One short sentence with zero filler and the effect front-loaded. It is efficient, though for a destructive operation the terseness borders on under-specification rather than ideal economy.

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?

An output schema exists and annotations cover the safety profile, so the description does not need to explain return values. Still, for an irreversible mutation the description omits how to locate the target id and what else is destroyed, which an agent would need in order to act confidently.

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% for the single `id` parameter, so the schema already documents it. The description adds nothing about the id's format, where to source it (presumably list_webhooks), or what happens if an unknown id is supplied, so 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?

"Stop deliveries to one of your webhook endpoints" names a concrete resource and the observable effect, so an agent can tell this acts on a webhook rather than a post or account. However, it never uses the word "delete" and never distinguishes itself from siblings like create_webhook, list_webhooks, or test_webhook, leaving the permanence of the action to inference.

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 statement of when to use this tool versus alternatives, no mention that list_webhooks is how you obtain the id, and no note that test_webhook exists for verifying an endpoint without removing it. The agent must infer all routing decisions from the tool name alone.

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