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

Annotations already declare the operation read-only and closed-world; the description adds substantial behavioral context by enumerating the exact returned fields and explaining what happens when no public page exists. That fallback behavior is especially useful for an agent deciding whether to call this tool.

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 front-loaded and every clause carries useful information about outputs or fallback behavior. It is somewhat dense as a single long sentence, which slightly reduces scannability, but there is little wasted text.

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?

There is no output schema, so the description must explain return values, and it does so thoroughly: identifiers, structure, supplier count, price range and confidence, carbon footprint details, citation URL, and no-page fallback. Nothing essential for correct invocation appears missing.

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 coverage is 0%, so the description must carry the parameter semantics, and it does: the identifier may be a CAS number, InChIKey, or name. This is exactly the missing information an agent needs to supply the required argument correctly.

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?

States a specific verb (retrieve) and resource (everything SharpSyn publishes about one compound). The identifier types and the enumerated payload make the scope unmistakable and distinct from search-oriented siblings.

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?

The description clearly indicates this is a single-compound detail retrieval keyed by an identifier and covers the fallback when no public page exists. It does not explicitly name search_compounds or list_suppliers as alternatives, so sibling routing is only implied.

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