delete-webhook-subscription

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

With no annotations, the description carries the full burden. It discloses the key consequence ('This will stop all webhook notifications'), which adds useful behavioral transparency. However, it does not mention irreversibility, authentication requirements, or behavior when no subscription exists. 'Delete' already implies destruction, so this is minimally adequate but not rich.

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 sentences that front-load the action ('Delete the current webhook subscription') and then immediately state the consequence. Every word earns its place; no fluff or redundancy.

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 0-parameter delete tool with no output schema, the description covers the purpose and the primary behavioral effect. It lacks details about error cases, irreversibility, or return values, but these are not strictly necessary for such a straightforward tool. It is complete enough for an agent to invoke correctly.

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 tool has zero parameters and the schema is empty, so the description need not explain parameter semantics. The baseline for 0 params is 4, and there is nothing to add.

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 tool's function: 'Delete the current webhook subscription for this account.' This uses a specific verb and resource, and the scope ('for this account') is explicit. It distinguishes itself from sibling tools like get-webhook-subscription and create-webhook-subscription.

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: to remove an existing subscription and stop notifications. While it does not explicitly mention alternatives or exclusions, the context is sufficient for an agent to understand this is for deletion rather than retrieval or creation.

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