Delete Subscription Offer

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

With no annotations, the description carries the full burden of behavioral disclosure. It does disclose important preconditions and the read-only mode restriction. However, it does not explicitly mention permanence, irreversibility, or what happens to associated data after deletion, which is a meaningful gap for a destructive operation.

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 extremely concise and well-structured: the core action is stated first, followed by two essential constraints. Every sentence earns its place, and there is 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 destructive operation, the description includes the key eligibility constraint and the read-only mode limitation. Since an output schema exists, return-value details are not required. It could further explain permanence or error behavior, but the essential information for invoking the tool correctly is present.

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%, and each parameter has a clear one-line description, so the tool description does not need to repeat parameter details. The description adds no extra semantic context beyond the schema, such as parameter relationships or examples, so the baseline score of 3 is appropriate.

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 the action and resource: 'Delete a subscription offer.' It also adds a differentiating eligibility condition (inactive offers with no active subscribers), which helps distinguish it from mutation siblings like patch or deactivate. However, it does not explicitly contrast itself with sibling tools such as deactivate_subscription_offer.

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 clear usage context by specifying that only inactive offers with no active subscribers can be deleted, and that the tool is disabled in read-only mode. This helps an agent decide when deletion is possible, though it does not name alternative tools for active offers or when-not-to-use scenarios.

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