Show plans and get an upgrade link

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

The description adds significant behavioral context beyond the annotations: it explains that the link opens a Stripe payment page, that nothing is charged unless the user pays, and that for existing subscriptions it opens the dashboard plan page. These details help the agent understand the tool's real-world effects.

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 what is returned and followed by behavioral context. The first sentence is dense with a parenthetical list, but no words are wasted and the structure is generally efficient.

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?

Given the lack of an output schema and the presence of annotations covering safety, the description provides a complete picture: what is returned, how the link behaves, and the subscription edge case. Nothing essential is missing for an agent to call it correctly.

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 coverage is 100%, so parameter meanings are already fully documented in the schema. The description only briefly reiterates the 'next plan up' default for the plan parameter, adding little beyond what the schema provides.

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 states a specific verb+resource: returns paid plans, current plan, and a checkout link. It clearly distinguishes the tool's scope and output, making it obvious what the tool does without needing to open the schema.

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?

Usage is implied (e.g., to view plans or get an upgrade link), but the description does not explicitly say when to use this tool versus siblings like my_account or when not to use it. The note about existing subscriptions opening the dashboard plan page provides context but not explicit guidance.

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