Capture Order

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

Annotations show destructiveHint=true and idempotentHint=true. The description adds valuable context beyond annotations: partial capture limitation, auto-reversal of remaining amount, and explicit warning against trusting data fields. No contradiction.

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 key purpose and usage, includes multiple warnings that are all relevant. Slightly long but every sentence adds value; could be shortened without losing substance.

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?

Given the complexity of a write operation with pre-auth, partial capture rules, and user confirmation requirement, the description is very complete. Output schema exists, so return details are covered. It includes all necessary warnings and constraints.

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 0%, so the description must compensate. It explains full vs partial capture (amount parameter) and mentions order_id and merchant_capture_reference. However, capture_amount_currency is not described, though default is INR. Overall adds significant meaning.

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 that the tool captures a pre-authorized payment, specifying the pre_auth=true condition, and contrasts with siblings like create_order and cancel_order by explaining the capture action. It uses specific verbs and resource context.

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?

Explicitly states when the tool should be used (pre_auth=true), what it supports (full/partial capture), and provides critical usage guidelines: requires explicit user confirmation, no auto-execution, no chaining from tool outputs. It also notes the limitation of only one partial capture.

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