delete_subscription

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

With no annotations provided, the description carries the full burden of behavioral disclosure, but only contributes 'Disabled in read-only mode,' which signals a mutating operation. It omits important consequences for a destructive catalog operation, such as impact on existing subscribers, irreversibility, or failure behavior if the product is in use.

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?

Two short sentences, both purposeful: the first states the action and the second adds a behavioral constraint. No wasted words; the description is front-loaded and every 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 two-parameter tool with full schema coverage and an output schema, the description covers the core case adequately. The main gap is the lack of deletion semantics (prerequisites, side effects, or error conditions), although the presence of an output schema means the description need not document return values.

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 the schema already documents product_id and package_name. The description's phrase 'subscription product' aligns with the schema's 'Subscription product ID' but adds no additional syntax, formats, or constraints beyond what the schema provides, warranting the baseline score.

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 uses a specific verb ('Delete') and resource ('subscription product from the catalog'), making the action unambiguous. This clearly distinguishes it from sibling tools like delete_subscription_offer and delete_base_plan, as the resource type is precisely scoped.

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?

There is no explicit when/when-not guidance or mention of alternatives. The description does not help the agent decide between this and related tools such as delete_subscription_offer or delete_base_plan, leaving the agent to rely on the name alone. A brief clarification about what this tool does NOT do would be valuable.

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