Delete a webhook endpoint

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

Annotations already declare destructiveHint=true and idempotentHint=false, so the safety profile is covered. The description goes further by naming concrete downstream consequences ('delivery, audience membership, published data or irreversible state'), the confirm requirement, and secret redaction/local-file behavior — genuine added context.

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?

Four short sentences, with the action and its consequences front-loaded before the confirm requirement. The trailing sentence about redacted response secrets and locally saved signing secrets is somewhat tangential to a delete operation, keeping it out of the top score.

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 mutation with full annotation coverage, no output schema, and complete parameter descriptions, the definition covers consequences, the confirm gate, and credential handling — enough to call it correctly. The only gap is the absence of any routing hint versus delete_webhook.

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 (account, confirm, webhook_endpoint_id) are already documented in the schema. The description only restates the confirm=true requirement and adds nothing about the id format or account resolution, so 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 opens with a specific verb+resource ('Delete a webhook endpoint'), so the core action is unambiguous. It does not, however, differentiate itself from the sibling delete_webhook, nor explain how endpoint-level deletion relates to it, leaving the agent to infer the distinction.

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?

It states the operational gate ('Requires confirm=true'), which implies this is a high-caution action, and the schema reinforces when confirm should be set. But it never says when to choose this tool over delete_webhook or update_webhook_endpoint, so the selection guidance is only implied.

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