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

Annotations already declare readOnlyHint=false, openWorldHint=true, idempotentHint=false and destructiveHint=false, and the description adds real context: the buyer must open the link and review tax before anything is charged. It stops short of covering link expiry, whether repeated calls create duplicate links, or any auth/account prerequisites, so it is not fully complete for a non-idempotent external-facing write.

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 sentences, front-loaded with the action and outcome, then the shipping default, then the escalation rule. Every clause carries decision-relevant information and none is redundant.

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?

With annotations, a rich nested schema and an output schema present, the description covers purpose, flow, deferral of charge, and the sibling handoff. It leaves out link lifetime and idempotency-duplication behavior, which matter for a tool flagged non-idempotent.

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%, so the parameter definitions already carry the baseline semantics. The description still adds value by stating the default behavior when shipping_rate_id is omitted and by implying the business filter on items, going slightly beyond the structured fields.

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 ('Create a secure Stripe checkout link'), plus the qualifying scope ('items with published prices'), which lets an agent separate it from request_quote and the pricing/stock siblings without opening the schema.

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?

Explicitly routes the agent: pass the shipping option id from get_shipping_estimate or omit it for the lowest rate, and use request_quote instead for on-request-priced items or orders above payment limits. Both the alternative and the condition that selects it are named.

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