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

描述尝试说明行为特征（如“不包含其他企业分类的统计”“仅返回数量不返回名单”），但“不返回名单”与工具自身命名为 list 相矛盾，会严重误导 agent。此外未说明年份缺失时默认行为、园区名称匹配不中时的处理等关键执行语义。

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?

描述结构紧凑，使用了“涉及/不包含/典型问法”等标签，阅读起来较清晰；但“仅返回数量”与整体 list 主题矛盾，属于严重信息冗余而非有效简洁。Pricing 仅为附加 meta 信息，不会额外加分。

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?

该工具最重要的语义——返回年度注销企业名单还是数量——始终被“不返回名单”形成自相矛盾，导致上下文信息不可靠。虽然已有输出 schema 和参数 schema，但描述阶段就产生关键歧义，整体完整性不足。

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 已覆盖 park_name 和 year 两个参数的描述，并提供园区名称示例和年份示例。descriptions 本身也通过典型问法给出名称列表，但并未补充参数默认值、格式要求或精确匹配规则，因此未显著超出 schema 的已有信息，符合 100% schema 覆盖下的基线 3 分。

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?

开头的“基于具体园区名称当年注销的企业列表查询”看起来目标明确，但随后“仅返回数量不返回名单”与工具名中的“list”以及典型问法“企业名单”“企业列表”直接矛盾。这使得该工具到底返回名单还是数量变得含糊，无法让 agent 清晰判断用途。

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?

提供了典型问法，如“中关村软件园当年注销的企业名单”，能在一定程度上说明使用场景；但未说明与 park_close_company_num 等计数类工具的区分，且“仅返回数量不返回名单”这一句与典型问法互斥，导致使用指引自相矛盾，无法可靠指导工具选择。

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