Billing portal URL

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

With no annotations, the description carries the full burden and does well: it discloses that the call is non-mutating (returns a URL rather than acting), that a human must open it in a browser, and that self-hosted deployments get a 'billing not enabled' outcome instead of a URL. It omits whether the URL is user-scoped, expiring, or requires admin auth, which leaves some behavioral gaps.

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?

Three tight clauses: what it returns and what it is for, the human-in-the-loop requirement, and the self-hosted fallback. Nothing is wasted and the primary purpose is front-loaded.

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 tool with no output schema, the description explains the return payload ({ url }) and the human browser step, plus the self-hosted degenerate case. Lifetime/expiry of the URL and any auth prerequisites are the only notable omissions.

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 per the baseline this scores 4. The description adds no parameter information but none is needed.

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 artifact (a Stripe Billing Portal URL) and its concrete uses (see invoices, change card, cancel at period end), which clearly separates it from a checkout URL or a billing status read. It does not name the nearest siblings (billing_checkout_url, get_billing) explicitly, so the differentiation is inferred rather than stated.

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?

It gives a clear usage condition split by deployment: on hosted instances it is the way to manage billing, while on a self-hosted Reelsaw it simply reports that billing is not enabled. There is no explicit routing to alternatives, but the hosted/self-hosted framing supplies usable context for when the tool applies.

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