search_chemical_by_cas

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

No annotations are provided, so the description carries full burden. It only states it searches for information, but lacks details on behavioral traits such as read-only nature, authentication, rate limits, or error 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?

The description is extremely concise, consisting of two lines. The first line clearly states the purpose, and the second line defines the parameter without wasted words.

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?

Given the simplicity (one required param, output schema exists), the description is too minimal. It omits details like what constitutes 'chemical substance information', handling of invalid CAS numbers, or pagination. While output schema exists, the description still lacks completeness.

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?

The parameter description in the tool text (cas_number: 化学物质的CAS号) merely restates the schema title 'Cas Number' without adding format, validation, or example details. Schema coverage is 0%, yet no extra semantic value is provided.

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 the verb 'search' and the resource 'chemical substance information' by CAS number. It distinguishes from sibling tools 'get_chemical_info' and 'get_cid_by_name' by specifying the search method using 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?

No guidance on when to use this tool vs alternatives. It does not mention when not to use or provide context for selecting this tool over siblings like 'get_cid_by_name'.

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