Search Assays

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, so the description's behavioral disclosure is minimal. It adds that results are a page of AIDs and describes pagination, which is useful but not required beyond annotations.

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 sentences with no filler. Key information is front-loaded: purpose, search methods, return type, pagination, and follow-up tool.

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 presence of output schema, the description covers search scope, pagination, and next steps. It is complete for a search tool with no missing gaps.

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%, so baseline is 3. The description adds value by explaining the purpose of the return (AIDs), how pagination works (page past maxResults with offset), and the relationship between targetType and targetQuery examples. This enhances understanding beyond schema.

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?

Clearly states it finds PubChem bioassays associated with biological targets, listing specific search types (gene symbol, protein name, NCBI Gene ID, UniProt accession). This distinguishes it from sibling tools like pubchem_search_compounds.

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?

Explains pagination using offset and maxResults, and suggests exploring results further with pubchem_get_summary. Does not explicitly provide when-not or alternatives, but context is sufficient for a search tool.

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