Tạo VietQR động cho đơn hàng

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

With no annotations, the description carries the behavioral disclosure burden. It adds valuable context beyond the schema: the customer scans the QR, funds go to a virtual account, and MONA Pay fires a webhook. This explains the operational consequence of calling the tool, though it does not discuss idempotency, expiry, or failure modes.

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 short, front-loaded with the core action, and includes a useful behavioral sentence. The English summary is mildly redundant with the Vietnamese sentence but serves bilingual users without adding meaningful bloat.

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?

The tool has 13 parameters, no annotations, and no output schema, so the description should compensate for more. It explains the payment flow and webhook behavior, which is helpful, but it does not describe what the tool returns (e.g., QR image, URL, or ID), nor does it give guidance on prerequisites or when to prefer this over related Monapay payment tools.

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 62%, so the schema already documents most key parameters. The description adds a small semantic clue by saying 'điền sẵn số tiền + nội dung', which maps to the `amount` and `description` parameters, but it does not explain ambiguous optional parameters like `traceNumber`, `loyaltyCode`, or `voucherCode`.

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 explicitly states a specific verb ('Tạo'), resource ('mã VietQR động'), and context ('cho một đơn hàng qua ACB'). This clearly distinguishes it from siblings like monapay_create_checkout and monapay_cancel_qr, and adds behavioral specifics beyond the title.

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 implies when the tool should be used ('cho một đơn hàng' / for an order) and describes the QR flow, but it does not explicitly contrast it with alternatives such as monapay_create_checkout, monapay_link, or static QR generation. There are no exclusions or if-then routing cues.

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