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

Annotations already declare readOnlyHint=false, openWorldHint=true and destructiveHint=false; the description adds useful context that the interaction happens in an external Stripe portal and that the user (not the agent) performs card updates and cancellations. It does not say whether calling it creates a session, whether the link expires, or that no billing change actually occurs server-side, which matters because 'cancel the subscription' could be misread as an action the tool performs.

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?

A single front-loaded sentence: the core resource comes first, then the concrete capabilities. Nothing is padded or repeated from the title.

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?

With no parameters and no output schema, the description should at least imply the return value and link lifecycle; 'Link to the user's Stripe billing portal' hints at a URL but never states it is a returned link, nor anything about expiry or single-use behavior. It is adequate to call the tool, but leaves the agent guessing about the result.

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 disambiguate and the baseline applies. No misleading parameter-like language is introduced.

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 names a concrete resource (the user's Stripe billing portal) and enumerates what that portal enables (update card, download invoices, change/cancel subscription), which is far more specific than the tool name 'spur_manage_billing' alone. It does not, however, distinguish itself from the close sibling spur_show_billing_options, leaving the boundary between the two unclear.

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?

There is no statement of when to use this tool versus spur_show_billing_options, spur_get_billing_summary, or spur_change_plan, all of which sit in the same billing cluster. The presence of a near-identical sibling makes the missing routing guidance a real cost, not a formality.

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