Get ChEMBL Activities

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It does not mention read-only nature, rate limits, error handling, or what happens when no results are found. The description is minimal and adds little beyond the basic function.

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 a single sentence of 10 words, which is concise and front-loaded with the core action. However, it sacrifices completeness for brevity. It does not contain unnecessary text.

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 (not shown), the description need not explain return values. However, with 3 optional parameters, the description does not mention that at least one filter (target or assay ID) is likely needed, nor does it explain the default limit. It is minimally complete.

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 description coverage is 100%, so the schema already documents all parameters. The description adds context by naming 'bioactivity data' but does not elaborate on parameter details (e.g., limit default, requirement for at least one ID). Baseline 3 is appropriate since the schema covers the 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 verb 'Retrieve' and resource 'bioactivity data from ChEMBL', and specifies the two filtering methods (by target or assay ID). It distinguishes from sibling tools like 'search_chembl_compounds' which likely search for compounds, not activities. However, it could be more precise about what 'bioactivity data' includes.

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 no guidance on when to use this tool versus alternatives. Sibling tools include other database query tools (e.g., query_bindingdb, query_drugbank) that may overlap in functionality, but no exclusions or context are given.

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