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

Annotations only provide openWorldHint, so the description carries most of the behavioral burden; it adds exclusions, pricing, and the 'only returns count, not list' limitation. However, that limitation seems inconsistent with a list-returning tool and no pagination, read-only, or authorization context is disclosed, so transparency is only moderate.

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 compact and front-loaded with the core purpose, followed by exclusions and typical questions. The '涉及指标/类型' line somewhat duplicates the first sentence, and the ambiguous '仅返回数量不返回名单' clause reduces clarity, but overall it is not bloated.

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 two-parameter list query with an output schema and fully documented parameters, the description is mostly sufficient and the examples help ground the expected use. The unresolved contradiction between 'list' and 'only returns count' plus the lack of explicit sibling guidance leaves a meaningful completeness gap.

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 provides full descriptions and examples for both park_name and year, so the description adds no extra parameter-level meaning. With 100% schema description coverage, the baseline 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 first sentence explicitly states the operation: querying the list of companies with patents for a specific park name, and the typical question examples reinforce the list intent. However, the clause '仅返回数量不返回名单' conflicts with the tool's list name and does not explicitly differentiate it from the sibling park_have_patent_company_num, so it is not a perfect 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?

The description gives concrete typical question phrasings and states exclusions ('不包含：其他企业分类的统计'), which helps the agent recognize when this tool applies. It does not explicitly name alternative sibling tools such as park_have_patent_company_num, but the usage context is clear.

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