agent_checkout_pay

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

No annotations are provided, so the description carries the full burden. It discloses the payment method and token type, but doesn't state whether this is a destructive/irreversible action, whether it requires prior steps, or what happens on success/failure. For a payment tool, this is a significant gap.

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?

One sentence, front-loaded with the action and key detail. It's efficient, though it could add a bit more context without becoming bloated.

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 payment execution tool with no annotations and no output schema, the description is thin. It doesn't mention prerequisites (e.g., quote must be prepared), idempotency, or what the response contains. An agent would need to infer the full flow from sibling names.

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 0%, so the description must compensate. It explains what the shared_payment_granted_token is (Stripe token, spt_...), which adds meaning beyond the schema. However, it doesn't explain quote_id beyond its name, and the token format hint is minimal.

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 states a specific verb ('Pay') and resource ('quote') with a specific method ('Stripe Shared Payment Granted Token'), which clearly distinguishes it from checkout siblings like agent_checkout_quote or agent_checkout_status. It doesn't explicitly name a sibling, but the phase/token detail makes the 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?

The description implies this is the payment step after quoting/preparation, but it doesn't explicitly state when to use it vs alternatives like agent_checkout_prepare or agent_checkout_fulfill. The 'Phase 3' hint gives some context, but no explicit when/when-not guidance.

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