create_payment_order

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

With no annotations provided, the description carries full burden. It explains amount unit, merchant order uniqueness, multiple QR code display options, fallback behavior, and identifier saving for polling. This is substantial behavioral context beyond a simple 'create' statement.

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 a single paragraph with multiple sentences, conveying needed information but lacking structure (e.g., bullet points). It is moderately concise but could be better organized.

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 3 parameters, no output schema, and no annotations, the description covers purpose, parameters, and detailed post-creation behavior. It omits error handling and idempotency, but overall provides adequate context for using the tool.

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%, but the description explains two of three parameters: amount (in yuan) and merchant_order_no (unique identifier). Notify_url is not described. This adds value beyond the schema's type constraints.

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 starts with 'Create a cashier payment order', specifying a clear verb and resource. It distinguishes itself from sibling tools like query_payment_order and refund_payment_order, which serve different purposes.

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 provides detailed post-creation instructions (display QR code, fallback, save identifiers) and implies polling with query_payment_order. However, it does not explicitly state when to use this tool versus its siblings or mention prerequisites.

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