Delete webhook

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

Annotations already flag destructiveHint=true and idempotentHint=true. The description adds valuable context by stating the consequence of deletion ('Stops sending notifications'), which goes beyond the schema. This helps the agent understand the side effect of the operation.

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 exceptionally concise, with only two short sentences that convey purpose and effect. Every word earns its place—no filler or redundant information.

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 tool with one well-documented parameter and no output schema, the description is complete. It states what it does, the effect, and the parameter is fully described in the schema. Annotations cover the safety profile (destructive, idempotent).

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 input schema provides 100% coverage with a clear description for webhook_id ('ID of the webhook to delete'). The tool description does not add additional parameter semantics, but the schema already fully explains the parameter, so a baseline score 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 clearly states the action ('Delete a webhook by ID') with a specific resource and identifier. It also differentiates from sibling tools by explicitly noting the effect ('Stops sending notifications'), making the tool's purpose unambiguous.

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?

The usage context is clear: this tool deletes a webhook. While it doesn't explicitly mention when not to use it or name alternatives, the delete action is distinct among siblings (create, list, get webhooks), so the intended use is evident. No exclusions are stated, but none are necessary for such a straightforward deletion tool.

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