batch_get_hazard_genetox_details

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is fully covered. The description adds nothing beyond that—no batch-size limits, partial-failure behavior, ordering, or rate-limit context—so it contributes no behavioral value of its own.

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 sentence with zero waste and the key scope word 'multiple' placed up front. It is efficiently sized, though it is so terse that it borders on under-specification rather than tight conciseness.

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 not be explained, and annotations cover the safety profile. Still, for a batch retrieval tool the description omits batch cardinality limits and how per-chemical failures are handled, leaving gaps an agent would want covered.

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% for the single dtxsids parameter, which is already documented as 'Chemical identifiers (DTXSIDs)' with a minItems constraint. The description's 'multiple chemicals' only restates the array nature and adds no format or syntax detail, so the 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 ('genotoxicity detailed data') with the scope 'multiple chemicals', which distinguishes it from the singular get_hazard_genetox_details. However, it never names or contrasts with the singular or summary siblings, leaving the agent to infer the batch distinction from the name alone.

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?

No when-to-use guidance is given: nothing says when to prefer this batch variant over get_hazard_genetox_details or batch_get_hazard_genetox_summary, nor any prerequisite or batching limit. The 'multiple chemicals' phrasing is only an implied usage hint.

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