Deactivate Subscription Offer

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

With no annotations provided, the description carries the disclosure burden. It reports two meaningful behavioral traits: the effect on new subscribers and that the operation is disabled in read-only mode. It does not mention reversibility, permissions, or effects on existing subscribers, so it is not fully transparent, but it is substantially informative.

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, each earning its place. The primary action and effect are front-loaded, followed by the read-only guard. No redundant or filler wording.

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 state-change tool with full parameter documentation and an output schema, the description is mostly complete: it states the effect, the resource, and the read-only restriction. It could be more complete by naming the inverse (activate_subscription_offer) or clarifying the difference from deletion, but nothing essential for invoking the tool is missing.

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 all four parameters are already documented in the input schema. The description adds no parameter-level detail, matching the baseline of 3 for full schema coverage.

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 and resource ('Deactivate a subscription offer') and adds a precise behavioral outcome ('making it unavailable to new subscribers'). This clearly distinguishes it from sibling operations like activate_subscription_offer and delete_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 effect 'making it unavailable to new subscribers' implies when the tool should be used, but it does not explicitly state when to choose this over activate_subscription_offer or delete_subscription_offer, nor does it give exclusions or alternatives. The usage context is therefore only implied, not explicit.

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