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

No annotations are provided, so the description carries the full behavioral burden. It clearly states the core behavior (returns a Stripe Customer Portal URL), but it doesn't disclose whether this action creates a Stripe session, whether it depends on the caller's Stripe customer being active, or whether the URL expires. These traits are relevant but not severely missing for a simple 0-parameter read-style tool.

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 concise sentence with no filler. The key verb, resource, and distinguishing context ('human billing') are all front-loaded, and every word 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, no-output-schema tool, this description is nearly complete: it tells what the tool returns (a URL) and for whom (humans managing subscriptions/invoices). It omits minor context like whether an active subscription is required or how the URL is delivered, but nothing critical is missing for an agent to invoke it correctly.

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?

There are zero parameters and the schema is empty, so per the baseline for 0-parameter tools this score is appropriate. The description does not need to explain parameter meanings that don't exist.

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?

States a specific verb ('Get') and resource ('Striple Customer Portal URL') and adds the intended purpose ('subscription management and invoice history'). The parenthetical '(human billing)' clearly differentiates it from sibling billing_machine_pay, so an agent can tell which billing tool is for which audience.

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?

Gives a clear intended context: it is for human-facing subscription management and invoice history. This tells the agent when to call it, though it doesn't explicitly name alternatives or state when-not-to-use. The sibling tools (e.g., billing_machine_pay) plus its own phrasing make the use case discernible.

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