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

Annotations already indicate this is not read-only, not idempotent, and not destructive. The description adds that the subscription is 'manual' and 'non-renewing,' and that provider-backed recurring billing is out of scope, providing valuable behavioral context beyond the annotations without contradiction.

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 sentences, front-loaded with the primary action and a clear alternative. Every word contributes meaning, with no redundancy or unnecessary detail.

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?

The description effectively covers the tool's purpose and usage guidance, distinguishing it from subscription-related siblings like cancel_subscription, pause_subscription, and resume_subscription. With an output schema and full parameter schema coverage, it is sufficient for tool selection, though it could name the specific alternative action link tool for added clarity.

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 has 100% parameter description coverage, so all 8 parameters are already documented. The description does not add parameter-specific details but reinforces the manual/non-renewing nature, consistent with the autoRenew const false constraint. Baseline 3 applies.

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 tool creates a 'manual, non-renewing subscription record for a member,' using a specific verb and resource. It distinguishes from provider-backed recurring billing by directing to a subscription action link, making its unique scope explicit.

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 explicitly instructs to use a subscription action link for provider-backed recurring billing, providing a clear exclusion. It implies this tool is for manual, non-renewing subscriptions, offering useful guidance among many subscription-related siblings, though it does not name the specific sibling tool.

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