delete-subscription

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

Annotations already indicate destructiveHint=true. The description adds that 'No further change notifications will be sent' and that deletion stops notifications. This provides some behavioral context beyond annotations, but does not detail other effects (e.g., permanence).

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 concise with a front-loaded purpose and a helpful tip. It uses three sentences plus a tip, without unnecessary words. Could be slightly more structured, but overall efficient.

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?

Given the tool is destructive with 4 parameters and no output schema, the description covers the main purpose, usage context, and references the permissions table. It lacks explicit return value description, but the schema's excludeResponse parameter addresses that partially. Overall adequate.

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 fully documents the four parameters. The description does not add additional meaning for any parameter beyond the schema. Baseline 3 is appropriate as the description adds no extra semantic value.

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 'Delete a subscription' and specifies that it deletes a webhook subscription, distinguishing it from list-subscriptions which is used to find the id. The verb and resource are specific and 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 description provides context: 'Use this to clean up stale subscriptions or stop receiving notifications' and suggests using list-subscriptions to find the id. It also references the Permissions section for supported resources. No explicit when-not-to-use guidance, but adequate for the tool.

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