batch_get_bioactivity_data

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

The annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is fully covered elsewhere. The description adds nothing behavioral beyond the noun 'batch' in its title – no mention of the 200-item cap, error/partial-failure behavior on a batch, or rate limits. With rich annotations the bar is lower, but the description contributes essentially no extra context.

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?

A single, front-loaded sentence with zero filler; the batching scope is stated immediately. It is arguably too terse to earn a 5, but nothing in it is wasted.

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 an output schema present and 100% schema coverage, the description does not need to explain return values or parameter details. It supplies the batching scope, which is the key missing piece for the agent, though it could be stronger by routing to the singular sibling.

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 both parameters (identifier_type enum and identifiers array with minItems/max 200) are fully documented in the schema. The description adds no syntax, format, or value guidance beyond what the schema already provides, making the baseline 3 appropriate.

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 states a specific verb (fetch), resource (bioactivity data) and scope (batch, multiple identifiers), which is enough to distinguish it from the singular sibling get_bioactivity_data. However, it never names that sibling explicitly, so the distinction relies on the agent inferring it from 'batch' vs. the sibling's singular name.

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?

'for multiple identifiers' implies the selection condition (use this when you have more than one identifier), but there is no explicit when-to-use statement and no reference to get_bioactivity_data as the single-identifier alternative. Usage is inferred rather than stated.

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