Open the Stripe customer portal; returns the hosted URL

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

Beyond readOnlyHint=false and openWorldHint=true, the description discloses the POST endpoint, the confirm:true execution gate, and the absence of a server-side dry run. These details substantially clarify execution safety, although authorization prerequisites and URL or session limitations are not covered.

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?

One compact statement front-loads the purpose and result, then provides the endpoint and execution safeguard. There is no filler, and the dry-run caveat 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 simple two-parameter tool, the description covers the operation, result, endpoint, and execution guard, including return information that is absent from an output schema. It could still clarify prerequisites, whose Stripe customer is used, URL or session behavior, and when to prefer it over the other billing tools.

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%, and both confirm and idempotencyKey are already documented there. The description mostly repeats confirm's role, adding only the useful clarification that there is no server-side dry run.

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 specifies the action and resource—opening the Stripe customer portal—and states that it returns the hosted URL. It does not explicitly distinguish this flow from billing_checkout, billing_overview, or billing_referral.

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 confirm gate explains how to preview versus execute, but that is primarily invocation mechanics rather than guidance about when this flow is appropriate. No alternatives or exclusions are named, so selection among the billing siblings remains implied.

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