pubchem_search

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds nothing behavioral: it doesn't say whether a name search returns a single best match or a list of candidates, nor anything about external-API rate limits or failure modes on ambiguous names.

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?

One short front-loaded sentence with no filler; the action and target come first. Nothing redundant is included.

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?

For a one-parameter search with no output schema, the description is minimally sufficient to make the call but incomplete: the agent cannot tell what is returned (CIDs, full records, multiple hits) or how an ambiguous common name is resolved.

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 100% and the single parameter is documented with examples, so the schema carries the load. The description's 'by name' only restates that, adding no matching rules (exact vs. fuzzy, case sensitivity, synonyms/IUPAC names).

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 and resource ('Search PubChem for a chemical compound'), so the agent knows exactly what it does. It does not distinguish itself from the sibling pubchem_properties, which likely takes an identifier and returns compound data, leaving the agent to infer the boundary.

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 phrase 'by name' implies the input mode but there is no explicit when-to-use or when-not-to-use guidance, and no mention of the obvious alternative (pubchem_properties). The agent gets no routing signal for the common case of 'I have a CID, not a name'.

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