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

Annotations already declare destructiveHint=true and openWorldHint=false, so the safety profile is covered. The description adds one genuine behavioral fact beyond that — that pending deliveries stop — but it does not say whether deletion is permanent, whether delivery history is retained, or whether the endpoint can be recreated/recovered.

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 short sentence with zero filler, front-loading the action and resource. It is not padded, though it is arguably under-written rather than tightly optimized.

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 whose annotations and schema are fully specified, the description covers the essential what and one side effect. It still leaves irreversibility and the sibling-tool choice (desk_delete_webhook vs delete_webhook) unaddressed, which matters for a delete operation.

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 100% with only two parameters, both documented in the schema ('webhook endpoint UUID' and the 'purpose' field). The description adds no syntax, format, or lookup guidance beyond that, 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 ('Deletes') and resource ('a webhook endpoint'), plus a consequence ('stops its deliveries'), so the agent knows exactly what the call does. It does not differentiate from the near-identical sibling 'desk_delete_webhook' or from 'delete_webhook', which an agent must disambiguate on its own.

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 when-to-use or when-not-to-use guidance, no mention of the alternatives (desk_update_webhook to disable, desk_delete_webhook vs delete_webhook), and no prerequisites such as permissions or confirmation. The agent must infer all routing from the name alone.

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