delete_webhook

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

With no annotations provided, the description carries the full burden. It discloses key behavioral traits: irreversibility and the fact that delivery history is retained server-side while the subscription stops receiving events. This goes beyond the bare operation name and gives the agent important safety information.

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 concise sentences: the first states the action, and the second covers key consequences. There is no extraneous information, and the structure is front-loaded with the verb.

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 delete operation with one parameter and an output schema, the description sufficiently covers the essential behavior (irreversibility, retention of history). It does not need to explain return values since an output schema exists, though it could optionally mention preconditions like the subscription needing to exist.

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 0% and the description does not mention the subscription_id parameter at all. While the parameter name is self-explanatory, the description fails to add any meaning beyond the schema, such as specifying that this ID identifies the webhook to delete.

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 opens with 'Delete a webhook subscription,' which is a specific verb+resource that clearly states the tool's action. It distinguishes itself from sibling tools like create_webhook, get_webhook, and update_webhook by using the explicit 'delete' verb.

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 on the outcome: delivery history is retained, the subscription stops receiving new events, and the action is irreversible. However, it does not explicitly mention when to choose this over alternatives (e.g., update_webhook to disable), so it lacks explicit exclusions.

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