Start Potarix Checkout (one-time card capture)

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

Description adds context beyond annotations: reveals human interaction requirement and relation to future charges. No contradiction but could mention potential failure scenarios or timeout.

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 compact sentences with no redundancy. Each sentence adds essential information.

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 low complexity and complete schema/annotations, description covers purpose, usage, and output handling. No output schema needed.

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 fully describes the single parameter 'tier_key' with enum and description. Tool description adds no additional param info, so baseline 3 is appropriate.

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 the tool returns a Stripe Checkout URL for one-time card capture. Distinguishes from sibling 'topup_credits' which handles subsequent charges.

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 says to hand the URL to the user and not follow it yourself. Also explains that after checkout, 'topup_credits' calls become silent off-session charges.

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