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

With no annotations, the description carries the full burden for a destructive operation, yet it says nothing about permanence, whether in-flight deliveries are cancelled, required scopes, or confirmation behavior. Only the REST mapping hints at the underlying semantics.

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?

Two short sentences with the action front-loaded and no filler. The REST-equivalence sentence adds some value as a semantics anchor, though it consumes space that could have gone to destructive-behavior disclosure.

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?

An output schema exists, so return values need no explanation, but for a permanent delete with zero annotation coverage and 0% parameter documentation, the description leaves out the details an agent needs to invoke it safely and correctly.

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 0% for two parameters. The description indirectly references webhook_id through the REST path, but never explains the api_key parameter (null by default) — whether it is required, how it authenticates, or whether it overrides a default credential.

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), which cleanly separates it from create_webhook, list_webhooks, test_webhook, and webhook_deliveries in the sibling list. It does not explicitly name those siblings, but the verb-resource pairing makes the intent 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 statement of when to use this versus alternatives, no prerequisites, and no warnings about consequences. The REST endpoint equivalence ('Same as DELETE /v1/webhooks/{webhook_id}') implies an irreversible single-resource removal but gives no operational guidance.

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