batch_get_hazard_toxref

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 by structured data. The description adds only the data source (ToxRefDB), and says nothing about batch size limits, partial-failure behavior, or ordering that would be genuinely useful for a batch call.

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 tight sentence with no filler and the key scoping term ('Batch') front-loaded. It is efficient, though the brevity borders on under-specification for a batch operation.

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, leaving little an agent strictly needs. Still, for a batch endpoint the description omits any note on batching semantics or how it relates to get_hazard_toxref, so it is only minimally complete.

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 parameter, so the schema already documents dtxsids as an array of chemical identifiers. The description's 'by DTXSID' merely restates this with no added format or cardinality 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?

The description states a specific verb (retrieve) and resource (ToxRefDB data) keyed by DTXSID, and the 'Batch' prefix distinguishes it in kind from the singular sibling get_hazard_toxref. However, it never explicitly names the sibling or states the batch-vs-single relationship, so an agent must infer the 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?

There is no guidance on when to use this tool versus get_hazard_toxref or the other hazard batch tools, and no stated preconditions or batch-size limits. The only implied usage is 'multiple DTXSIDs', which comes from the name rather than the description.

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