batch_search_hazard

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 only adds the batch/multi-DTXSID nature, which is already implied by the name, and says nothing about response size, limits, or how batching behaves. Marginal value beyond structured fields.

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 efficient sentence that is front-loaded with the key verb and scope. No filler, though it is arguably under-specified rather than genuinely concise.

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, and annotations carry the safety profile. Still, the routing ambiguity against search_hazard and the per-dataset batch_get_hazard_* tools leaves the agent without enough to call this correctly versus alternatives.

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 the schema already documents dtxsids, summary, and data_type with an enum. The description mentions 'multiple DTXSIDs' and 'selected dataset' but adds no syntax, format, or enum-value meaning beyond what the schema supplies. 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?

States a clear verb (batch lookup), resource (hazard), and scope (multiple DTXSIDs, selected dataset). However, it fails to distinguish itself from closely related siblings such as search_hazard (single lookup) and the per-dataset batch_get_hazard_toxval/skin_eye/cancer/genetox/toxref tools. An agent cannot tell from the description alone whether this tool subsumes those or is a separate generic path.

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, when-not-to-use, or alternative routing is provided. 'For the selected dataset' implies the data_type parameter drives selection but gives no guidance on choosing between this generic batch tool and the more specific batch_get_hazard_* siblings.

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