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

The annotations already declare destructiveHint=true, so the key value-add is the description's disclosure that the delivery log is deleted along with the endpoint — collateral damage an agent would not otherwise know, and one that matters before calling. It does not mention that repeat deletion will fail (non-idempotent), but the safety profile is already covered by annotations.

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 sentence, front-loaded with the operational consequence ('stop posting events') before the destructive act, with no padding.

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 delete with no output schema, the description gives the essential facts: what stops, what is removed, and that the delivery log goes too. Only the ID source and failure behavior on repeat calls are 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 description coverage is 0% for the single required webhook_endpoint_id, and the description adds nothing about it — no note on where the ID comes from (list_webhook_endpoints, get_webhook_endpoint) or what happens if it is stale. The parameter is inferable from the tool name, but the description does not compensate for the coverage gap.

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 concrete effect plus resource: it stops event posting to a URL and deletes the webhook endpoint. That clearly separates it from update_webhook_endpoint and get_webhook_endpoint, though it never names those siblings explicitly.

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 choose this over disconnecting via update_webhook_endpoint or inspecting deliveries with list_webhook_deliveries first. The description states the outcome but leaves the decision context and any prerequisites entirely to inference.

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