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

Annotations declare readOnlyHint=false and destructiveHint=true, but the description usefully reframes this: the tool itself only mints a link, and 'Changes happen there, made by the user' clarifies that mutation is external and user-initiated rather than performed by the call. That is real added context beyond the annotations, though it stops short of stating auth or expiry behavior for the generated link.

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 short sentences, front-loaded with the action and outcome. The trailing 'Changes happen there, made by the user' partially restates the earlier 'where the user manages their Pro subscription', but the emphasis on user-driven external change 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?

For a zero-parameter, open-world tool with no output schema, the description covers what it does, what the resulting portal contains, and who performs the changes. It could be stronger by noting that it returns a URL to hand to the user, but nothing essential for invoking it correctly is missing.

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. The description correctly avoids inventing arguments and instead spends its words on scope and outcome.

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: 'Creates a link to Stripe's billing portal', scoped to Pro subscription management (payment card, invoices, billing cycle, cancellation). An agent knows exactly what the tool does. It does not, however, distinguish itself from the sibling start_pro_checkout, which is the nearest competing billing 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?

Usage is implied by the enumerated portal capabilities (card, invoices, billing frequency, cancellation), so an agent can infer this is the 'manage existing subscription' path. But there is no explicit when-to-use vs. when-not, and no routing to start_pro_checkout for the new-subscription case, leaving the primary ambiguity unresolved.

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