batch_get_exposure_functional_use

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, covering the safety profile. The description adds nothing beyond that — no batch-size ceiling, no partial-failure behavior, no rate-limit or missing-ID handling.

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 no filler, so nothing is wasted. It is arguably under-specified rather than over-long, which the conciseness dimension should not penalize heavily.

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 described. For a batch tool, though, the absence of any guidance on list size, ordering, or handling of unknown IDs leaves a real gap that annotations do not fill.

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?

With one parameter at 100% schema description coverage, the schema already documents dtxsids as a list of DSSTox Substance Identifiers. The description's 'batch' wording implies a plural input but adds no format, limit, or validation detail beyond the schema.

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 clear verb (batch fetch) and resource (reported functional use data), and the 'batch' qualifier distinguishes it from the singular sibling get_exposure_functional_use. However, it never names that sibling or explains the batch-vs-single distinction explicitly.

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 when-to-use guidance, no mention of the single-item alternative, and no indication of batch-size limits or prerequisites. The agent must infer that this is the multi-ID variant purely from the word 'batch'.

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