batch_get_chemical_details

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 covered. The description adds nothing on top: no batch size limits, no behavior for unknown/invalid identifiers, and no partial-failure semantics.

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, but it is under-specified rather than tight - there is room for one or two more sentences that would earn their place by covering batching and sibling routing.

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, but for a batch mutation-free lookup with enum-driven parameters, the description omits batch limits, identifier-format expectations, and how it relates to the singular sibling tool. That leaves gaps an agent must guess at.

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 both enums (id_type, subset) are documented in the schema, so the baseline is 3. The description adds no format details for identifiers or explanation of what each subset returns.

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+resource ('Get detailed information about ... chemicals') and the batch scope via 'multiple'. It is distinguishable from get_chemical_details by the plural/batch framing, but it never explicitly contrasts itself with that sibling or with batch_search_chemical.

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, no exclusions, and no mention of alternatives such as get_chemical_details for a single chemical or batch_search_chemical for discovery. The agent must infer that this is the bulk lookup path.

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