Delete webhook

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

Annotations already declare destructiveHint=true, idempotentHint=false, readOnlyHint=false, and openWorldHint=true, which carries the safety profile. The description adds nothing beyond that: it does not state that deletion is irreversible, that the 'confirm' flag is a required safety gate, or what happens to dependent objects.

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 front-loaded sentence with no filler or redundancy. It is efficiently written, though for a destructive operation the extreme brevity borders on under-specification rather than ideal economy.

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?

Annotations and the fully documented schema carry most of the load, and there is no output schema to explain. Still, for a destructive, non-idempotent delete the description says nothing about irreversibility or the confirm requirement, leaving the agent to reconstruct the safety story purely from structured fields.

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 all three parameters (id, account, confirm) are already well documented in the schema, including the important confirm-gating semantics. The description's 'with the given ID' adds only a trivial restatement, 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?

The description gives a specific verb and resource ('Delete a webhook'), so the operation is unambiguous at a glance. It does not, however, distinguish itself from siblings like update_webhook, create_webhook, or get_webhook, which the definition leaves the agent to infer from the names alone.

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 when-to-use or when-not-to-use guidance, no mention of prerequisites, and no reference to alternatives such as update_webhook or the list/get siblings. The agent gets no help deciding whether deletion is the right call here.

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