listEarnCoupons

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

No annotations provided, so description carries full burden. It includes rate limit (10 req/s) and states returned card states, but does not explicitly confirm read-only behavior or describe side effects. Adequate but not exhaustive.

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?

Efficiently structured: purpose sentence, states returned types and statuses, provides clear application guidance with bullet points, and ends with rate limit. No fluff.

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?

No output schema, so description should detail response fields. It mentions awardId and specCode in usage context but does not fully describe the response structure or pagination. Some gaps for agent completeness.

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%, but the description explains that the single parameter 'category' determines which product's coupons to query, and lists the allowed values (FlexibleSaving, DualAssets) in context. This adds meaning beyond the raw enum.

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 the verb 'Query', specifies the resources (interest-rate coupons and Dual Assets reward cards), and scopes it by product category. It distinguishes itself from sibling tools like getEarnPosition and getEarnProduct by focusing on coupon listing.

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 usage by linking to place-order requests, but lacks explicit guidance on when to use this tool vs alternatives (e.g., getAwardInfo). No when-not-to-use or prerequisite information.

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