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

Beyond the annotations, it discloses that the link is single-use and short-lived, only works after a subscription exists, and is refused with a specific error if billing is not enabled. It also warns against constructing portal URLs manually, giving agents critical behavioral constraints the annotations do not cover.

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?

The description is detailed but every sentence earns its place: primary purpose first, then uniqueness, prerequisite, failure mode, and action guidance. The bolded error warning is placed prominently and the whole text remains scannable.

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?

Despite having no output schema, the description clearly conveys what is returned (a link) and what the agent should do with it. It covers prerequisites, alternatives, error handling, and follow-up steps, making it complete for correct invocation and downstream behavior.

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 has zero parameters and schema description coverage is 100%, so there is no parameter meaning the description must add. Per the baseline for zero-parameter tools, this earns a 4 rather than a lower score.

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 the exact deliverable ('a link to the Stripe customer portal'), the intended user ('a human to open'), and the supported actions (change plan, update card, download invoices, cancel). It explicitly distinguishes itself from sibling tool `upgrade`, so an agent can select it unambiguously.

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 description states exactly when to use it (human-driven plan/card/invoice/cancellation needs), when not to use it (before first subscription, use `upgrade`), and what to do on failure (`billing_unavailable`, point to support). It even forbids retries, leaving no ambiguity.

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