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

行为说明超过openWorldHint=true的标注内容：描述明确告知包含哪些指标、不包含哪些内容，并限定不能用于披露合规评价或作为投资建议。由于absen没有readOnlyHint，描述使用“查询”一词也透露出只读行为，但没有进一步说明输出分页或数据口径。

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?

描述以要点形式组织，包含目的、指标、不包含项、典型问法和定价信息，整体简洁且重点突出。不过Pricing段落和部分“不包含”会有轻微重复和噪声，但未明显影响可读性。

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?

作为情一个2参工具且已有output 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?

input schema已经100%覆盖参数说明，company_name与country_name都有类型和示例。description的“典型问法”提供了自然语言的调用示例，例如“中国国比亚迪股份有限公司机构持股集中度”，但未增加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?

说明明确描述了工具的用途：在特定企业名称下查询资本品牌相关的周期性变化，并列出机构持股集中度、机构持股稳定性、公募基金家数、平均持股时间这4个指标。说明同时标注“不包含非本分类指标”和“按园区/产业链批量筛选”，有效区别于同类工具。

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.