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

Beyond annotations (non-readonly, non-destructive), the description reveals server-side price resolution and the fact that charging only occurs upon customer completion of Stripe Checkout. This adds valuable behavioral context without contradiction.

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?

Two sentences cover purpose, usage guidance, and behavioral nuance without any wasted words. Front-loads the core action and legacy/modern distinction.

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 three parameters with oneOf and a clear output schema, the description adequately covers the essential behavioral and usage aspects. Minor omission: no mention of required authorization or catalog setup, but siblings imply the context.

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 coverage is 100% so baseline is 3. The description adds value by explaining the legacy vs. new parameter choice and confirming server-side price handling, which goes beyond the schema's field descriptions.

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 explicitly states the tool creates a hosted checkout URL for merchant-catalog products, distinguishing it clearly from sibling tools that handle products or integration instructions.

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?

It advises new integrations to use 'items[]' over legacy 'productId' input, and clarifies that the tool contacts Stripe but does not charge the customer. Lacks explicit when-not-to-use scenarios, but guidance is solid.

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