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

Annotations already declare destructiveHint=true, so the destructive nature is known. The description adds a specific behavioral requirement not present in annotations: 'Requires owner/admin.' This is meaningful context that helps the agent anticipate authorization failures. It does not contradict any annotation and adds value beyond the structured metadata.

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?

The description is extremely concise: one sentence for the core action and a short permission note. It is front-loaded with the purpose and contains no fluff. Every word earns its place.

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 single-parameter delete operation with an output schema present and destructiveHint annotation, the description covers the essential points: what it does and who can do it. It does not elaborate on side effects or irreversibility, but these are implied by the destructive annotation and the simple nature of the operation. It is adequate, though not exhaustive.

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%; the webhookId parameter already has a clear description ('Webhook ID to remove from this deployment.'). The tool description adds no additional parameter-level detail, so it does not improve on the schema. Baseline 3 is appropriate.

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 states a clear verb-resource pair: 'Remove a registered webhook.' This unambiguously identifies the operation and distinguishes it from sibling tools like webhooks_list (list) and webhooks_set (create/update). The title 'Delete a webhook' reinforces the purpose.

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?

The description provides no guidance on when to use this tool versus alternatives. It only mentions a permission requirement ('Requires owner/admin'), which is a prerequisite, not usage context. There is no mention of scenarios, conditions, or exclusions relative to other webhook tools.

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