delete_webhook_destination

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

The description discloses destructive behavior beyond the destructiveHint annotation: it removes queued deliveries from the store, requires confirm=true, returns success=false without confirmation, and acts as a no-op without confirm. This gives the agent a precise safety model.

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 well-structured with a clear summary, behavioral note, and argument list. There is minor redundancy around the confirm requirement appearing three times, but it remains compact and readable.

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 two-parameter destructive operation, the description covers the action, consequences, confirmation safeguard, and the related create operation. With annotations and a complete input schema, no critical information is missing for an agent to call it safely.

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%, so the schema already documents both parameters fully. The description repeats the parameter meanings without adding significant new detail beyond what the schema provides.

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 first sentence states a specific verb ('Delete') and resource ('webhook destination and queued deliveries'), making the operation unmistakable. It also contrasts with create_webhook_destination, which helps distinguish it from the most closely related sibling.

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 clearly establishes when this tool is appropriate: to permanently delete a webhook destination and its queued deliveries. It names create_webhook_destination as the alternative for adding a destination, though it does not discuss temporary disabling via set_webhook_destination_enabled as a non-destructive alternative.

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