Delete a webhook endpoint

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

Annotations already flag destructiveHint=true, but the description goes well beyond them: it says the deletion is permanent and irreversible, that the delivery log is destroyed alongside the endpoint, and that two scopes (webhooks:write and delete) are required. That is exactly the auth and blast-radius context an agent needs before a destructive call.

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 clauses, front-loaded with the permanent/destructive fact, then the permissions, then the confirmation gate, then the safer alternative. No filler sentences.

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?

Covers destructiveness, irreversibility, required authorization, required user confirmation, and the safer sibling alternative; no output schema is needed for a delete. Only the parameter-level detail is left to the schema, which is acceptable for a one-field tool.

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 the single endpointId parameter, and the description never mentions it or explains how to obtain it. The name is largely self-describing and format=uuid constrains it, so the gap is tolerable, but this is the one place the description adds nothing.

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 and resource ('Permanently delete a webhook endpoint') plus the collateral scope ('and its delivery log'). This is clearly distinguishable from the sibling update_webhook, which handles pausing.

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?

Gives an explicit when-not: 'to pause it instead, use update_webhook with isActive false', naming the sibling and the exact parameter value. It also prescribes the human-in-the-loop gate ('Confirm with the user before calling').

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