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

Even though annotations indicate destructive and idempotent behavior, the description adds a meaningful operational consequence: event delivery stops immediately. This helps the agent understand the real-world effect of the call. No contradiction with annotations.

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 two short, front-loaded sentences with no filler, repeated information, or schema duplication. It covers action and consequence concisely.

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 tool, the description plus schema is sufficient to know what to pass and what happens. It could have mentioned that the webhook ID can be found via list_webhooks, but this is not necessary for correct invocation.

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 only parameter, webhookId, is fully described in the schema (type string, required, description 'Unique identifier of the webhook to delete'). The tool description adds no additional parameter semantics, so it does not exceed the baseline set by the schema.

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 uses a specific verb ('Delete') and a specific resource ('a registered webhook'), and the added consequence 'Event delivery stops immediately' makes the tool's purpose unmistakable and differentiates it from sibling delete tools like delete_document or delete_file.

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 description provides clear context for when to use the tool: remove an existing webhook and immediately halt event delivery. It doesn't explicitly mention alternative operations or edge cases, but for a single-purpose delete tool the usage context is unambiguous.

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