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

Annotations declare readOnlyHint=false and destructiveHint=false, which is somewhat confusing for a tool that only returns a link; the description resolves this by explaining the actual mutating actions (updating card, cancelling) happen in the external Stripe portal, not here. That is meaningful added context beyond the annotations. It doesn't cover auth requirements or rate limits, hence not a 5.

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 sentences, zero waste. The 'what it does' sentence comes first, followed by the routing condition. Every clause earns its place.

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?

An output schema exists, so the return value (the portal link) need not be re-explained, and the description correctly focuses on purpose and routing. The only gap is the missing differentiation from upgrade_plan for plan-change requests.

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 tool takes zero parameters, so there is nothing for the description to clarify; baseline is 4. No spurious argument discussion is present, which 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?

Specific verb+resource: 'Get a link to the Stripe billing portal', with concrete scope (view invoices, update card, cancel subscription). An agent immediately knows this returns a URL, not a modification. It does not distinguish itself from the sibling upgrade_plan, which is the one adjacent tool a user query could plausibly route to.

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?

Explicit trigger condition: 'Use when the user asks to manage, change, or cancel their billing/subscription.' This is clear routing guidance, but it gives no exclusion against upgrade_plan, which is the obvious alternative for plan-change requests.

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