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

描述明确使用“查询”表述，说明这是只读操作，并披露了输入条件和返回的核心字段；同时给出了每次运行 0.2 credits 的定价信息，这在输入 schema 和 annotations 中都没有体现。未说明无结果时的行为或数据变动边界，但基于其查询类工具的定位，已具备足够透明度。

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?

描述由一个信息密集的核心句和一个定价说明组成，没有冗余填充。核心功能、操作方式、关键返回内容一句话内交代清楚，结构性好，便于快速理解。

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 和 annotations 已足以支撑 Agent 完成一次对外投资信息查询；主要缺失是未提及与最相近查询工具的区分，但实际使用影响有限。

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 对 company_name、page、limit 三个参数都有完整说明，覆盖率为 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?

描述用明确的动词和资源说明功能：“查询该企业的对外投资信息”，并列举了被投资方公司名字、开业时间、投资金额、公司状态、投资比例等关键字段，目的清晰。但没有明确与 company_holding、chain_invest_company_list 等同级工具做区分，因此未达到完全满分。

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?

“基于明确指定的企业名称”暗示了适用场景是已有准确企业名称时需要查询其对外投资信息，具备一定的使用指引。但没有说明在模糊名称、无投资信息或与其他投资类工具之间应如何选择，也没有明确排除条件，因此属于“隐含用法”。

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