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

Annotations already declare idempotentHint=true and destructiveHint=false. The description adds real behavioral context beyond them: login is required, it queries the source of truth, PAID means only payment while completed=true means entitlement issuance, and it neither creates orders nor issues refunds. This is meaningful disclosure the annotations do not provide.

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 login requirement is front-loaded in brackets, and the remainder is dense with no filler. Sentences are compact and each carries operational meaning. It is slightly information-packed but not padded.

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?

For a single-parameter lookup with no output schema, the description covers the key interpretive states (PAID vs completed), the correct follow-up behavior when issuance is pending, and the boundaries (no order creation, no refunds). An agent has enough to call and interpret it, though it omits the return shape.

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% for the single parameter outTradeNo. The description partially compensates by indicating the input is an order number ('按订单号'), which maps to outTradeNo, but adds no format, length, or sourcing detail. Baseline is not reached because the schema does no documentation work here.

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 and resource: verify ('回源核验') the caller's own payment and invoice result ('本人付款及发票结果') by order number. This distinguishes it from siblings like create_payment_order, cancel_payment_order, and get_my_tickets_and_pass. It does not explicitly name a sibling, so it stops short of a 5.

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?

It gives operational next-step guidance ('未发放继续查或联系工作人员，勿再付款' and '查不到不能断言扣款失败'), which implies when the tool is useful. However, it does not compare against sibling tools (e.g. get_my_tickets_and_pass) or state exclusions in a routing sense, leaving usage only partially implied.

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