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

The description claims '仅返回数量不返回名单', which contradicts the tool name and typical usage expecting a list. No other behavioral details (auth, rate limits) are provided. The openWorldHint annotation doesn't mitigate the internal contradiction.

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 includes redundant pricing information and a contradictory phrase, making it less concise. The core content is okay but the extra details and inconsistency harm clarity.

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?

The description is incomplete due to the return-type contradiction, which is critical for an agent deciding between list and count tools. Output schema exists, but the description fails to clarify the actual return behavior, leaving a significant 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?

Schema descriptions cover both parameters (100%). The description adds example park names but no additional syntax or semantics beyond the schema, meeting the baseline for high coverage.

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 it queries a list of enterprises surviving over 5 years for a specific park, distinguishing from the num sibling. However, the phrase '仅返回数量不返回名单' (only returns quantity, not list) contradicts the tool's purpose, introducing ambiguity and reducing clarity.

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?

Typical questions give context (e.g., '中关村软件园存续5年以上的企业名单'), implying usage for list requests. It does not explicitly contrast with the num counterpart or state when not to use, but the examples partially compensate.

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