Get Bioactivity

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

The description discloses behavioral traits beyond annotations: it explains pagination (offset, maxResults) and the effect of filters on the result set. Annotations already indicate read-only and idempotent, which the description does not contradict. There is no destructive behavior, and the description adds useful context about what data is returned.

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 is extremely concise with just two sentences. The first sentence defines the tool's purpose and outputs, and the second explains filtering with an example. Every word adds value; there is no redundancy or fluff.

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 tool has 6 parameters, rich annotations (readOnly, openWorld, idempotent), and an output schema (implied by context signals), the description is complete. It covers the primary functionality, filtering, pagination, and a use case. No gaps are evident.

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 filtering (e.g., 'focus the profile'), suggesting how to obtain the cid (using pubchem_search_compounds), and providing an example query. This goes beyond the schema's property descriptions.

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 verb 'Get' and the resource 'bioactivity profile', specifying what data is returned: assays, outcomes, target identifiers, quantitative values. It distinguishes from sibling tools like pubchem_get_compound_details by focusing on bioactivity rather than general properties.

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 a concrete example ('is this compound active against target T?') and explains how to use filters to focus results. While it doesn't explicitly compare to sibling tools, the example gives clear guidance on when to use filtering. A slight improvement would be mentioning when this tool is preferred over others.

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