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

Beyond the openWorldHint annotation, the description discloses the return semantics: the result is a merged text return containing total/production/sales/dependency counts. It also states what is not included. It does not detail edge cases or the exact response structure, but the output schema supplies that minimal gap.

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 well organized and front-loaded: the purpose appears first, followed by metric types, exclusions, and typical questions. The pricing detail is extra but harmless; overall the text is concise and scannable.

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 simple count/aggregation tool with two required parameters, the description is sufficiently complete: it defines the metrics, the input scope, the exclusions, and provides example utterances. The only real omission is an explicit pointer toward chain_have_no_patent_company_list when the user actually wants raw company-level data.

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?

The input schema already fully documents all parameters with 100% coverage. The description reinforces them through realistic region/chain/year examples, but adds little beyond what the schema already provides, so a baseline score of 3 is appropriate.

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 exact function (querying the count of companies with no patents by region and industry chain) and distinguishes itself from list-like siblings by clarifying it returns only merged counts for total/production/sales/dependency types and excludes company rosters.

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 gives explicit limits ('不包含：其他企业分类的统计；企业名单明细') and practical example questions. It does not explicitly name the list counterpart tool, but the exclusion phrase strongly implies that a separate list tool should be used when enterprise details are needed.

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