unsubscribe

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

With no annotations, the description carries the behavioral disclosure burden. 'Remove' clearly signals a destructive mutation, and 'returned from subscribe' provides a precondition, but the description does not disclose idempotency, error behavior for unknown ids, or side effects beyond the removal 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?

A single sentence with no filler; the action, resource, and id provenance are front-loaded and each word earns its place.

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 one-parameter destructive operation with no output schema, the description provides the essential call information: what to do and which id to use. It does not document response or error shape, but the tool's low complexity makes the missing detail a minor 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 coverage is 100%, so the schema already documents subscription_id. The description adds value by identifying the id as one returned from subscribe, which helps an agent know where to obtain it.

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 a precise verb ('Remove'), the exact resource ('webhook subscription'), and the selection mechanism ('by its id'). It also distinguishes the tool from siblings like subscribe and list_subscriptions by making the destructive action explicit.

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 phrase 'returned from subscribe' gives clear context about where the id comes from and implies this tool is used after a subscription has been created. It does not explicitly list when-not-to-use or name alternatives, so it misses the top score, but the usage context is clear.

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