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

Annotations declare destructiveHint=true and idempotentHint=true, but the description adds what is actually destroyed (cart cleared, stock/rewards reserved), the payment-synchronization behavior, the possibility of finalizing an already-paid order, and the crucial non-obvious fact that no payment is captured here. This is exactly the beyond-annotations context the dimension rewards.

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?

Six tight sentences, front-loaded with purpose, then prerequisite sequencing, then per-provider constraints, then side-effect warnings. No filler, and each sentence carries distinct 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?

Return values are covered by the output schema and the annotation profile is reinforced, so the description is nearly complete for a tool of this complexity. The remaining gap is the undocumented required/optional parameters (idempotency_key, confirmation_id) and how payment_scope relates to payment_method, given 11 params at 0% schema coverage.

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?

With 0% schema description coverage and 11 parameters, the description must carry the parameter burden. It meaningfully explains expected_total/expected_currency (must match the get_checkout_summary approved total) and ties addresses/discounts/points to that prior call, but leaves idempotency_key, confirmation_id, payment_mode, and payment_scope, including how payment_method='online' differs from the named providers, undefined.

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?

States a concrete verb (Create) and resource (hosted checkout), names the supported providers, and lists the transactional side effects (reserving stock/rewards, clearing the cart) that distinguish it from siblings like get_checkout_summary or resume_payment. An agent can separate it from every neighboring tool without opening a schema.

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?

Gives explicit sequencing ('First call get_checkout_summary... submit its approved total/currency'), plus branch constraints (international delivery requires Razorpay in delivery currency; Paytm is domestic INR only). It covers preconditions and conditional eligibility, not just a vague 'use this to pay'.

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