billing_portal

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

No annotations are provided, so the description must disclose behavior. It does not state whether this is a read-only operation, whether it requires authentication, or whether it has side effects such as generating a session. The terse phrase offers no behavioral context.

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 extremely short, but this is under-specification rather than efficient conciseness. It is front-loaded but lacks the substance needed for a tool whose purpose is not self-evident from the name alone.

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?

There is no output schema, no parameter details, and the description provides no information about return values, expected inputs, or preconditions. Given the ambiguity and lack of annotations, this is completely inadequate for an agent to call the tool 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?

The tool has zero parameters, so the schema fully covers parameter semantics (coverage 100%). Baseline for 0 params is 4, and the description does not need to explain parameters that do not exist. No value is added, but none is required.

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 is a noun phrase, 'Stripe Customer Portal URL', with no verb or action stated. It does not clarify whether this tool creates, retrieves, or generates a portal URL. Sibling tools like create_login_link and billing_checkout suggest related functionality, but without a verb the purpose remains ambiguous.

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?

No guidance is provided on when to use this tool versus alternatives. Among siblings such as billing_checkout, billing_machine_pay, and create_login_link, there is no indication of which scenario this tool addresses, leaving the agent to guess.

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