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

With only an openWorldHint annotation, the description carries the behavioral burden. It discloses the merged return format ('合并返回总量/生产型/销售型/依赖型文本') and scope exclusions, adding useful context beyond the annotation, though it does not mention auth, rate limits, or result details.

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 front-loaded with purpose, followed by a concise include/exclude list and example queries. The embedded Pricing JSON is arguably extraneous but not distracting; overall the content is efficient and well-structured.

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 the schema and the clear sibling pattern, the description covers what the tool returns, what it excludes, and typical query phrasings. It does not discuss pagination or result limits, but the presence of an output schema likely covers return structure, making this sufficiently complete for selection.

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 100%, but the description adds value by specifying region granularity ('国家，省份，城市，区县'), concrete chain_name examples, and typical year usage via example questions, going beyond the schema's basic field descriptions.

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 states a specific verb ('查询') and resource ('A级纳税人企业列表'), scoped by region and chain name. It also enumerates sub-types (total/production/sales/dependent) and excludes count-only queries, clearly distinguishing it from sibling *_num tools.

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?

Usage is clear: use for region + chain name A-level taxpayer list queries. Explicit exclusions ('不包含：其他企业分类的统计；仅返回数量不返回名单') tell the agent when not to use this tool, though it does not explicitly name the alternative chain_a_taxpayer_company_num.

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