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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the safety profile is covered. The description adds nothing beyond that: it does not say the deletion is permanent, whether it can be undone, whether it revokes any associated delivery endpoints, or what permissions are required. For a destructive operation it contributes no behavioral context of its own.

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?

A single four-word sentence with zero padding, front-loaded with verb and resource. It is efficient rather than verbose; the only cost is that the brevity leaves behavioral gaps unaddressed elsewhere.

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?

The tool is simple (one fully documented parameter, no output schema) and annotations carry the destructive/safety signal, so the description is close to sufficient. It is still missing the two things an agent would want before an irreversible delete: confirmation that the operation is permanent and whether related resources are affected.

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% and the single id parameter is already documented as 'The webhook ID to delete'. The description's 'by ID' phrasing adds no format, source, or lookup guidance beyond the schema, 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 (Delete) and resource (webhook) with the keying parameter (by ID), so an agent can distinguish it from update_webhook, get_webhook, and the unrelated delete_post/delete_media siblings without opening the schema. It stops short of any scope detail (e.g. workspace/account ownership of the webhook), but the purpose itself is unambiguous.

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 tool versus alternatives such as update_webhook (which could disable rather than remove) or rotate_webhook_secret, and no prerequisites or warnings about irreversibility. The agent must infer usage entirely from the name.

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