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

Goes well beyond the annotations by disclosing concrete side effects: it persists state, may finalize an already-paid order, and may send confirmation notices. This is consistent with readOnlyHint=false and destructiveHint=true while adding the specific consequences an agent needs before invoking, plus the explicit non-goal of initiating or capturing payment.

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 tightly written sentences: the primary action is front-loaded, followed by side effects and the boundary clause. No filler, and every clause adds operational meaning.

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?

An output schema exists, so return values need no explanation, and annotations already cover safety hints. The description covers side effects and boundaries well; the only meaningful gap is the absence of any guidance on the attempt_id input, which is the sole required parameter.

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 carry the burden. It contextualizes attempt_id as a 'customer payment attempt from Razorpay, Cashfree, PhonePe, or Paytm,' which hints at the identifier's origin, but never explains where to obtain it, its format, or its lifecycle, leaving the single required parameter only partially compensated.

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 specific verb (refresh) and resource (customer payment attempt), names the four gateways involved, and clarifies the persistence of server-verified state. The clause 'does not initiate or capture payment' further separates it from resume_payment/retry_payment, so an agent can distinguish it from siblings without opening schemas.

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 exclusion ('does not initiate or capture payment') gives a clear when-not, and the refresh/persist framing implies when to use it. However, it never names the alternatives (resume_payment, retry_payment, get_order) or states an explicit condition that selects this tool over them, so routing is partly left to inference.

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