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

The only annotation is destructiveHint=true, so the description carries most of the behavioral burden. It adds critical context that this moves money, charges a card, and can authorize or immediately capture, plus the POST /payments endpoint. It does not cover idempotency behavior, permission requirements, 3DS/authentication handling, or return behavior, so it stops short of exhaustive.

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 front-loaded with the critical action and money-movement warning, then gives the endpoint and required inputs. Every sentence earns its place with no filler.

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 destructive 11-parameter payment-creation tool, the description covers the core behavior and required invocation fields, while the schema documents the optional parameters. It omits return-value expectations and idempotency guidance, but remains sufficient to call the tool correctly.

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 100%, so the schema already documents all 11 parameters. The description repeats the three required parameters and source-object examples, but adds no syntax, constraints, or meaning beyond what the schema provides.

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?

Specific verb and resource: creates a payment and explicitly states it moves money by charging a card/payment source. It also distinguishes authorization from immediate capture and names the Checkout.com endpoint, so an agent can identify it as the charge-creation tool rather than a capture, refund, or void tool.

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 gives clear implied usage: use this when charging a payment source to create an authorization or capture. However, it does not explicitly say when to use this instead of siblings such as checkout_capture_payment, checkout_create_payment_link, or checkout_refund_payment, and it states no prerequisites or exclusions.

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