Archive Subscription

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

With no annotations, the description carries the burden of disclosing behavior. It clearly states that archiving preserves the record for existing subscribers and that deletion is rejected once purchases exist, communicating the non-destructive nature of the operation. However, it does not mention whether archiving is reversible or whether it affects active subscriptions.

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 two concise, purposeful sentences with the primary action front-loaded and the rationale immediately following. Every sentence adds value with 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 two-parameter mutation with an output schema, the description covers the purpose, usage conditions, and key behavioral distinction. An agent has enough information to invoke the tool correctly and understand its effect relative to alternatives.

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?

The input schema provides 100% description coverage for both required parameters (package_name and product_id), and the description adds no additional parameter-level context. Baseline 3 applies because the schema already documents the parameters adequately.

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 explicitly states the operation ('Archive a subscription') and clearly distinguishes it from deletion by explaining archiving is preferred over deleting purchased subscriptions. This differentiates it from the sibling delete_subscription tool.

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 provides explicit guidance on when to use archiving: for any subscription that has ever been purchased, because deletion is rejected once purchases exist. This gives the agent a clear condition for choosing this tool over the deletion alternative.

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