Delete Webhook

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

Annotations are absent, so the description carries the full burden of behavioral disclosure. It only says 'Delete a webhook,' which conveys destruction but does not disclose whether deletion is permanent, whether it affects active triggers, whether it requires specific permissions, or whether it is idempotent. The description adds no meaningful detail beyond the action itself.

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 a single sentence with no redundancy and is front-loaded with the action. However, it is terse to the point of adding little value beyond the title, so it does not earn a 5.

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 single-parameter delete operation with no output schema, the description is minimally viable: the target and action are clear. It omits relevant context such as irreversibility and permission requirements, which matter for a destructive tool, but the simplicity of the operation partly compensates for that gap.

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%, and the webhookId parameter is already documented in the input schema as 'The ID of the webhook to delete.' The description adds no parameter-level meaning, so the baseline of 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 states the action (delete) and resource (webhook) with a clear verb+noun structure. It distinguishes itself from sibling webhook tools (create_webhook, get_webhook, update_webhook) through its deletion verb, though it relies on the tool name for that differentiation.

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 about when to use this tool versus alternatives like get_webhook or update_webhook. There are no prerequisites, no mention of when deletion is appropriate, and no warnings about consequences. The agent must infer usage solely from the sibling names.

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