Delete webhook

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

The description's 'DESTRUCTIVE' note merely echoes the existing destructiveHint=true annotation, adding no new behavioral context such as irreversibility, side effects, or authorization requirements. It repeats rather than extends what annotations already convey.

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 extremely concise, front-loading the action 'Delete a webhook endpoint' followed by the explicit warning 'DESTRUCTIVE.' Every word serves a purpose, with no filler or redundancy.

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 one-parameter delete tool with destructiveHint=true and full schema coverage, the description is adequate. It names the resource and action, and the annotation covers the destructive nature, making it sufficient for an agent to select and invoke the tool correctly.

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?

The schema fully documents webhook_id as 'Webhook endpoint UUID' with 100% coverage, so the description adds no extra meaning beyond the parameter name and type. Baseline score of 3 is appropriate since schema does the heavy lifting.

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 clearly states 'Delete a webhook endpoint,' using a specific verb and resource. It distinguishes from siblings like create_webhook, update_webhook, and list_webhooks by naming the delete action directly.

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 is provided on when to use this tool vs. alternatives, such as when to delete versus update or when it should not be used. The description only states the action without context or prerequisites.

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