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

Annotations already declare destructiveHint=true, readOnlyHint=false, and idempotentHint=false, so the safety profile is fully carried by structured data. The description adds nothing beyond that, giving no information about irreversibility, what happens to delivery history or logs, or whether confirmation is required for a destructive operation.

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?

It is short, but the single sentence is duplicated verbatim with no added information, which is pure waste rather than conciseness. Nothing is front-loaded because there is nothing to front-load.

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?

This is a destructive, non-idempotent mutation with a nested required object and no output schema, so the description was the only place to explain confirmation, irreversibility, and project scoping. It supplies none of that, leaving the definition inadequate for the tool's complexity.

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?

Top-level schema coverage is reported as 0% with a nested request object, so the description would need to compensate and does not. It never mentions the required webhook `id`, nor the `projectId` scoping rule, forcing the agent to read the nested schema to learn that projectId is required with an organization key.

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 is literally the tool title repeated verbatim ("Delete a webhook" twice), which is the definition of tautology against the name/title. An agent learns nothing about scope, and no sibling (webhooks-update, webhooks-retrieve) is distinguished.

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 instead of webhooks-update or webhooks-retrieve, no prerequisites, and no note that deletion is permanent. The agent must infer the entire usage decision from the tool name.

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