pay_checkout

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

With no annotations provided, the description fully discloses behavioral traits: settles on Solana, 99% instant transfer to merchant, spends from agent or owner wallet, irreversible, and refuses paid/expired sessions. No contradictions.

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?

The description is well-structured and covers all necessary points without redundancy. Slightly verbose due to technical details like ADR-008, but still efficient. Could be trimmed slightly.

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?

For a single-parameter tool with no output schema or annotations, the description provides complete context: payment flow, wallet modes, prerequisites, and restrictions. No gaps remain.

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%, and the description adds meaning: session must be 'pending', amount/token are fixed by merchant, and it accepts UUID or full URL. This enhances clarity beyond the schema's basic description.

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 clearly states the verb (pay) and resource (pending Solinkify Pay checkout session). It distinguishes from sibling tools like pay_get_session and spend_authority_status by specifying 'pending' status and the settlement process.

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?

Explicit guidance: check spend_authority_status when owner wallet is used, confirm amount with pay_get_session first, and note that paid/expired sessions are refused. Clearly differentiates from read-only tools.

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