get_chemical_info

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

无注释信息，描述仅说明'获取详细信息'，未披露行为特性（如读操作、幂等性、速率限制等）。虽隐含只读性质，但未明确，且未提及返回格式或副作用。

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?

考虑到工具简单且有输出模式，描述应说明返回数据的类型和内容（如性质、用途等），但仅提'详细信息'，未涉及输出结构或检索范围，完整性不足。

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?

模式覆盖率为0%，描述为'name'参数添加了中文解释'化学物质名称'，补充了模式中仅有的'Name'标题。但未提供格式、限制或示例，缺乏深度。

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?

描述明确说明工具用于获取化学物质的详细信息，即从名称获取详细数据。但与同级工具（如get_cid_by_name、search_chemical_by_cas）的区别未明确，且未指明返回数据的具体范围。

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?

描述未提供何时使用此工具而非替代方案的指南。未提及与其他工具（如通过名称获取CID或按CAS搜索）的比较或条件，缺乏适用场景说明。

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