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

Annotations already declare readOnlyHint=true and openWorldHint=false, and the description adds genuinely useful behavior beyond that: calling sends nothing, the user fills in quantities and submits the request themselves. That is exactly the kind of non-obvious detail annotations can't convey, though link lifetime or failure behavior is not covered.

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?

Two tight sentences, the output (a link) is front-loaded, and the caveat about nothing being sent follows immediately. No waste.

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?

With one simple parameter, no output schema, and annotations covering the safety profile, the description supplies what's missing: the return type (a link) and the fact that no request is dispatched. Nothing an agent needs in order to call it correctly is absent.

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% and the lone `identifier` param is an undescribed string, but the description compensates by defining accepted formats – CAS number, InChIKey, or name. That is material guidance a caller could not get from the schema, though nothing is said about invalid or unmatched identifiers.

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 names a concrete output (a link the user opens) and its purpose (requesting a supplier quote for a compound), which is clearly distinct from the lookup-oriented siblings. It stops short of explicitly naming when to prefer a sibling like get_compound, but an agent can still tell what this produces.

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?

Usage is only implied: it's for when a user wants suppliers to quote on a compound. There is no explicit when-to-use/when-not or reference to the siblings get_compound, list_suppliers, or search_compounds, so the agent must infer the routing.

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