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

Annotations already declare readOnlyHint=false and destructiveHint=true, so the safety profile is covered structurally. The description adds nothing beyond that: no statement of irreversibility, no permission requirements for the superadmin-only customerId path, no note on side effects such as invalidating deliveries.

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 is front-loaded and waste-free, but at this length it reads as under-specification rather than disciplined brevity. There is no room for structure to evaluate.

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 destructive mutation the description omits the one thing an agent cannot infer from structured fields: that deletion is permanent and what it cascades to. Annotations and a complete schema carry the mechanical details, but the description leaves the operation's consequences unstated.

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%, so both webhookId and the superadmin-only customerId are fully documented in the schema itself. The description adds no syntax or format 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?

"Delete a webhook endpoint" is a bare restatement of the tool name delete_webhook; it names a verb and resource but adds no scope, target system, or distinguishing detail. It is effectively a tautology, though it is not misleading.

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?

No when-to-use guidance, no alternatives named (e.g., update_webhook vs delete_webhook), and no conditions or prerequisites described. An agent gets zero routing help from the description text.

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