APIbase

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

No annotations are provided, so the description carries the full burden. It discloses what data is returned (GHS classifications, pictograms) and the data source (PubChem/NCBI), but lacks information on error handling (e.g., invalid CID), data availability (not all compounds have GHS data), or rate limits.

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?

Excellent structure: front-loaded action ('Get GHS...'), immediate expansion of the GHS acronym, specific enumeration of return values, and closing context (safety assessments). No wasted words; every clause provides distinct value.

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 tool's simplicity (single required parameter) and lack of output schema, the description adequately covers the domain by explaining GHS components and safety assessment use cases. Would benefit from noting data availability limitations or error scenarios, but sufficiently complete for a lookup tool.

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?

With 100% schema description coverage for the single 'cid' parameter, the baseline score applies. The description reinforces that the CID returns GHS classification data, but does not add semantic details beyond the schema such as example CIDs, format constraints, or lookup behavior.

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 explicitly states 'Get GHS... hazard classification for a compound' with specific details on returned data (signal words, H-codes, P-codes, pictograms). This clearly distinguishes it from sibling chemistry.pubchem.* tools which handle properties, structures, or bioassays rather than safety classifications.

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?

Provides clear usage context with 'Essential for chemical safety assessments,' indicating when to use the tool. However, it lacks explicit guidance on when NOT to use it (e.g., for general physical properties) or direct references to sibling alternatives like chemistry.pubchem.properties.

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