pubchem-mcp-server

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

While annotations confirm read-only/idempotent behavior, the description adds valuable context about the data structure returned (assay lists, quantitative binding constants, target protein names) and the domain meaning of 'activity outcomes.' This helps the agent understand what constitutes a 'bioactivity profile' beyond the 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 well-constructed sentences with zero waste. The first front-loads the core capability and data types (assays, outcomes, targets, quantitative values); the second provides actionable filtering guidance. Every clause earns its place.

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 100% schema coverage, present annotations, and an existing output schema, the description appropriately focuses on domain semantics (bioactivity terminology like IC50/Ki) rather than repeating structural details. The level of detail matches the tool's complexity.

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%, establishing a baseline of 3. The description adds semantic value by explaining the investigative purpose of the outcomeFilter ('focus on active results' for understanding biological profiles), which helps the agent select appropriate parameter values beyond the raw schema enums.

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 uses a specific verb ('Get') and clearly identifies the resource ('compound's bioactivity profile'). It distinguishes from siblings by detailing unique bioactivity-specific content (assays, IC50/EC50/Ki values, target gene symbols) that none of the other compound tools provide.

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?

Provides clear guidance on using the outcomeFilter parameter ('focus on active results'), implying when to filter versus retrieving all records. However, it lacks explicit comparison to sibling tools (e.g., when to use this versus pubchem_search_assays or pubchem_get_compound_details).

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