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

Annotations already declare readOnly=false, openWorld=true, idempotent=false, and destructive=false. The description adds meaningful context beyond those: payment details remain on a hosted page, and 'opening the page alone confirms nothing', clarifying that no local state change is guaranteed by the call itself. It does not cover authentication or failure behavior, keeping it from a 5.

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?

Three compact sentences, front-loaded with the action. The second sentence handles privacy behavior, and the third handles confirmation semantics. Every sentence earns its place with no waste.

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?

An output schema exists, so return-value explanation is unnecessary. For a non-idempotent, open-world action, the description covers what happens, where payment data lives, and what must be done afterward. It stops short of covering error or authentication cases but is otherwise sufficient.

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?

Schema description coverage is 100%, and the single order_id parameter is already fully documented in the schema. The description adds no further parameter-level meaning, so the baseline of 3 applies.

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 and resource: 'Open secure billing for this account's order or subscription'. The purpose is immediately clear and consistent with the tool name. It does not explicitly name sibling alternatives like create_checkout or get_order, so it falls short of a 5.

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 phrase 'when the user asks' gives only implied usage, and there is no explicit comparison against create_checkout or get_order. However, it does provide a valuable follow-up rule: 'Read the order after returning to confirm any change', which guides post-invocation behavior.

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