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

The description discloses behavioral constraints beyond the openWorldHint annotation, such as excluding other enterprise-category statistics and asserting 'only returns quantity, not list'. However, this assertion conflicts with the list-oriented tool name, so the transparency value is weakened by confusion.

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 first sentence is front-loaded and the example questions are helpful, but '涉及指标/类型：没有专利的企业列表' is redundant with the first sentence, and the Pricing block is irrelevant to tool selection. The description is readable but not tightly edited.

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?

Despite a low parameter count, high schema coverage, and an output schema, the description leaves a critical ambiguity: whether this tool returns a list or a count. It also fails to clearly differentiate from the sibling count tool, so an agent cannot confidently select or invoke it.

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 description coverage is 100%, so the description adds little over the schema. The typical questions provide concrete park_name examples, but no additional syntax, defaults, or parameter relationships that are not already in the schema.

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 opens with a clear 'list query of no-patent enterprises by park' and gives typical questions asking for lists, but then states '仅返回数量不返回名单' (only returns count, not list), which directly contradicts the tool name and stated purpose. This makes the actual behavior misleading.

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 typical questions provide some usage context, but there is no explicit when-to-use note or alternative differentiation from the sibling count tool 'park_have_no_patent_company_num'. The confusing 'only returns number not list' clause actively undermines correct tool selection.

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