delete-subscription

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

Annotations already indicate destructiveHint: true and readOnlyHint: false. The description adds value by clarifying that after deletion, 'No further change notifications will be sent,' which is a key behavioral outcome not captured by annotations alone.

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 moderately concise at six lines, including a tip and a cross-reference. It is well-structured with a main statement followed by a tip, though the tip could be slightly shortened without losing clarity.

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 destructive delete operation with no output schema, the description covers purpose, usage context, and a prerequisite. It mentions the required subscriptionId implicitly via cross-reference, but does not detail optional parameters like If-Match or includeHeaders. Overall, it provides sufficient context for 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?

Schema description coverage is 100%, so baseline is 3. The tool description does not add any additional meaning to the parameters beyond what the schema provides (e.g., 'If-Match' as ETag is already described). No parameter guidance is given in the description.

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 elaborates with a tip about webhook subscriptions and stopping notifications. It is specific about the resource and action, but does not explicitly differentiate from sibling tools like 'update-subscription' or 'reauthorize-subscription', though the tip mentions using 'list-subscriptions' for finding the ID.

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 explicitly states when to use the tool: 'clean up stale subscriptions or stop receiving notifications.' It also references a related tool 'list-subscriptions' to find the ID, providing sequential context. However, it does not specify when not to use it or alternatives for pausing notifications.

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