get_bioactivity_data

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is fully covered. The description adds only that results are 'detailed' and scoped to one identifier, offering little beyond the structured fields about projection behavior or result breadth.

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; it is appropriately sized. It could carry a little more routing information without bloat, so it is efficient but thin rather than exemplary.

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 values need no explanation, and the annotations cover safety. However, with this many closely named bioactivity siblings, the description is too sparse to fully route an agent correctly.

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 identifier, identifier_type (with its enum), and projection are already documented in the schema. The description adds no format hints, valid-ID guidance, or projection semantics, so baseline 3 is 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?

It states a specific verb+resource ('Retrieve detailed bioactivity data') and narrows the scope with 'for a single identifier', which implicitly separates it from the batch_get_bioactivity_data sibling. It does not, however, distinguish it from the many summary/aed/assay bioactivity siblings that also operate on single identifiers.

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 gives no when-to-use guidance, no conditions for selecting it over get_bioactivity_summary_by_dtxsid, get_bioactivity_aed, or the batch variant. The only implicit cue is the word 'single' in an environment dense with alternatives.

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