Delete webhook

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

Annotations already declare destructiveHint=true, idempotentHint=false and readOnlyHint=false, so the safety profile is covered. The description adds genuine operational context beyond that: provider scopes/locks/credits apply, confirmation is mandatory before execution, and only one submission is accepted, reinforcing the non-idempotent/irreversible nature.

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?

Two terse sentences front-loaded with the endpoint identifier, with no filler. The confirmation warning is placed after the operation identity, which is reasonable, though phrasing is slightly dense.

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 delete with no output schema, the description covers the required acknowledgment (confirm), the one-shot submission rule, and financial/safety implications well. It stops slightly short of describing failure or error behavior, but is broadly complete.

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 67%; uid carries a pattern/length constraint and account and confirm have their own schema descriptions. The description adds no parameter-level meaning beyond the structured fields, so the baseline of 3 is appropriate.

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+resource via the REST endpoint 'DELETE /v5/webhooks/{uid}', which unambiguously identifies it as a webhook deletion operation. It distinguishes itself from the get/list/create/update_webhook siblings by the distinct verb, though it doesn't name alternatives explicitly.

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?

Usage is implied by the destructive verb and the note that confirmation is mandatory, but there is no explicit guidance on when to delete a webhook versus updating it or which sibling to prefer. An agent can infer the context but gets no stated conditions or exclusions.

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