subscriptions__customer_portal_link

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

With no annotations provided, the description discloses key safety information: 'this tool never moves money'. It also indicates the URL is 'bearer-owned', implying authentication requirements. No contradictions with hypothetical annotations.

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 a single, well-structured sentence with a bracketed context prefix, front-loading essential information without unnecessary words.

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?

Given the simple one-parameter input and no output schema, the description sufficiently covers the tool's return value (URL) and non-monetary nature. It does not mention error cases or detailed authentication, but for this tool that seems adequate.

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 schema has 0% description coverage and the only parameter, `account_id`, is not explained in the description. The description does not clarify what `account_id` represents or how it is used, leaving the agent to infer.

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 clearly states it 'Return a bearer-owned Stripe-hosted billing-portal URL', with the context prefix specifying the domain. This distinguishes it from sibling tools like subscriptions__create_checkout_link by focusing on portal access rather than checkout creation.

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 implies usage for enabling customer self-management of subscriptions via a portal. It notes 'the human manages or cancels there', clarifying the purpose, but does not explicitly mention when not to use it or alternatives among siblings.

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