Delete an outbound webhook

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

Annotations already declare destructiveHint=true, idempotentHint=false, and openWorldHint=true, so the safety profile is known from structured data. The description adds nothing beyond that: it doesn't say whether deletion is permanent, what happens to queued deliveries or delivery history, or whether re-deleting errors out.

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 a single short, front-loaded sentence with no filler, but that brevity comes from under-specification rather than efficiency—the one sentence adds almost no information.

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, non-idempotent mutation with no output schema and an undocumented parameter, the description should cover irreversibility, side effects, and how to supply the id. None of that is present.

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% and the single parameter subscription_id is documented only by its UUID format and pattern. The description never mentions the identifier, where to obtain it, or that it is required, so it fails to compensate for the coverage gap.

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 sentence only restates the tool name and title ("Delete" + "webhook subscription") with no additional scope, effect, or distinguishing detail. It does not separate this from siblings like list_webhooks or create_webhook beyond the obvious verb.

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 guidance on when to use this versus list_webhooks (to find the id), create_webhook, or any alternative removal path. No preconditions, no note about what to do if the subscription doesn't exist.

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