Delete a subscription

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

Annotations already mark destructiveHint true and readOnlyHint false, and the description adds important consequences: 'may notify recipients or change tenant data.' It also states the auth requirement and the need for confirm:true, going well beyond the annotations.

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 compact and front-loaded with the action and endpoint. Every sentence adds value: endpoint, body requirement, reference, permissions, and side effects. No filler.

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, the description covers the endpoint, required confirmation, permissions, and potential side effects. With destructiveHint in annotations and no output schema, nothing essential is missing for an agent to invoke this 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?

Schema coverage is 67%, and the description adds 'Body fields: none' and restates the confirm:true requirement, which reinforces the schema's confirm description. It doesn't elaborate subscriptionId, but the schema already documents it; overall it adds meaningful context beyond the schema.

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?

Description states the specific verb 'Delete' and resource 'a subscription', and includes the exact HTTP endpoint. It clearly distinguishes from sibling tools like get/modify/create subscription by naming the destructive action.

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 gives prerequisites (operator write opt-in and confirm:true) but does not explicitly say when to use this tool over alternative subscription operations (e.g., unsubscribe_a_user or modify_a_subscription). Usage is implied rather than explicitly contrasted with siblings.

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