subscriptions__customer_portal_link

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

With no annotations provided, the description carries the full burden. It discloses that the tool does not move money (safety assurance) and returns a bearer-owned URL. However, it lacks details on authorization requirements, error handling for invalid account_id, or rate limits. Some behavioral context is added but not exhaustive.

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 short (two sentences) and front-loaded with a bracketed context prefix. Every word contributes: it names the action, specifies the bearer ownership, and clarifies what the tool does not do. The bracketed part slightly adds length but offers useful domain context.

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 no output schema, the description adequately states the return value ('URL'). It covers the tool's scope and safety. However, missing parameter documentation is a gap; the agent lacks guidance on what account_id represents (e.g., format, where to obtain it). Overall adequate but incomplete.

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 input schema has one required parameter 'account_id' with no description, and schema description coverage is 0%. The description does not mention 'account_id' at all, leaving the agent to guess its purpose or format. No additional meaning is provided beyond the schema.

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 the tool returns a 'bearer-owned Stripe-hosted billing-portal URL'. The bracketed context specifies the domain (subscriptions, B2B monthly seats, etc.), and it distinguishes from sibling tools like create_checkout_link by focusing on the billing portal where human manages or cancels.

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 indicates usage for returning a portal link for human management ('The human manages or cancels there') and explicitly states what it does not do ('this tool never moves money'). However, it does not compare with alternatives like subscriptions__create_checkout_link or when exactly to use this over other subscription tools.

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