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

No annotations exist, so the description carries the full burden. It usefully discloses cost ($0.02 USDC per call) and that results are bilingual, but says nothing about whether this is a pure read, result caps, or rate limits — no contradictions, just gaps.

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?

Front-loaded with what is returned, then filters, then a runnable example, then price. Dense and mostly waste-free; the field enumeration is long but each item is informative.

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?

With only two optional parameters and no output schema, the description covers what an agent needs: which fields come back, valid category values, a usage example, and the billing model. Only the limit semantics and read-only assurance are missing.

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 fully compensates for category by listing the nine accepted values (treasury/credit/stock/bond/fund/commodity/newenergy/realestate/agri), which is real added meaning, but says nothing about limit beyond the example's value (e.g. default 20, maximum allowed).

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+resource (查 RWA 发行项目档案) and enumerates exactly which record fields come back (issuer, underlying asset, size, regulator, partners, dates, official source link, bilingual). This clearly separates it from list_datasets and query_market, though it never explicitly contrasts with the nearby query_projects or verify_rwa_project.

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 category filter and a concrete example call (query_issuances(category='treasury', limit=10)) imply the intended usage, and the billing note signals it is a paid, per-call lookup. There is no explicit statement of when to prefer this over query_projects or verify_rwa_project, so routing is left to inference.

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