pubchem-mcp-server

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and openWorldHint=true. The description adds that the tool returns assay IDs (AIDs) and implies the external data scope by mentioning UniProt and NCBI Gene IDs, aligning with openWorldHint. However, it omits error handling behaviors, rate limits, or what happens when no assays are found.

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 consists of two efficient sentences with no wasted words. The first establishes purpose and scope; the second covers input methods, return values, and workflow integration. Information is front-loaded and dense.

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 presence of an output schema and comprehensive input documentation, the description adequately covers the tool's purpose, return type (AIDs), and next-step workflow. It appropriately omits detailed return value explanations (covered by output schema) but could benefit from noting result size implications or error states.

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, the baseline is 3. The description reinforces the schema by listing example query types (gene symbol, protein name, etc.) but does not add substantive semantic meaning beyond what the input schema already documents for the three parameters.

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 clearly states the tool 'Find PubChem bioassays associated with a biological target,' providing a specific verb and resource. It distinguishes from sibling tools by explicitly mentioning that results 'can be explored further with pubchem_get_summary,' clarifying its role in the workflow versus 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?

The description provides workflow guidance by naming pubchem_get_summary as the follow-up tool for exploring returned AIDs. However, it lacks explicit guidance on when to use this assay search versus the compound search (pubchem_search_compounds) or when to prefer pubchem_get_bioactivity directly.

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