batch_get_bioactivity_assay_annotations

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

Annotations already declare readOnly, idempotent, non-destructive and open-world behavior, so the safety profile is covered. The description adds nothing beyond that — no note on what an 'annotation' contains, whether missing AEIDs are tolerated, or any batch-size limits.

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 short, front-loaded sentence with no wasted words. It is efficient, though its brevity is partly the cause of the missing usage and behavioral detail.

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?

An output schema exists, so return-value explanation is not required. However, for a batch retrieval tool positioned among dozens of bioactivity siblings, the definition is minimally adequate: it identifies the input but leaves routing and result semantics largely unexplained.

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% and there is a single required parameter, so the schema already documents 'aeids' as a list of assay endpoint IDs. The description's phrase 'for AEIDs' merely restates that without adding format or batch-size detail; baseline 3 applies.

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?

States a specific verb (retrieve) and resource (assay annotations) with a clear batch scope and the key selector (AEIDs). It is clear what the tool does, but it does not differentiate itself from adjacent bioactivity tools such as get_bioactivity_assay or get_bioactivity_aed by explaining what 'annotations' actually covers.

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?

There is no statement of when to use this tool rather than the many sibling bioactivity retrieval tools, nor any prerequisite or exclusion guidance. The agent must infer the use case entirely from the name, despite a crowded sibling set.

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