tier_checkout

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

Discloses key return value (Stripe checkout URL), indicating payment is handled externally. No annotations provided, so description carries burden. Does not mention authentication needs or side effects beyond checkout creation.

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, no wasted words. Purpose, alternative, identifiers, return value are all front-loaded and succinct.

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?

Returns value (Stripe URL) explained. No output schema present. Lacks error scenarios or prerequisites like account status, but sufficient for a checkout generation tool.

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 already covers 100% of parameters with descriptions, including tier pricing. Description adds context about payment method and identifier options, but not essential beyond 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?

Clearly states action (subscribe/renew/upgrade), target (run402 tier), and payment method (Stripe credit card). Differentiates from x402 on-chain payment, making purpose unambiguous.

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 presents as alternative to x402 on-chain payment, guiding selection between credit card and on-chain methods. Mentions support for wallet or email identifiers, though does not state prerequisites or when not to use.

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