Fetch Many

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

With no annotations the description carries the full burden. It usefully discloses the 100-item cap and the non-obvious behavior that it may return fewer results due to chemical-system deduplication, which is real value. However it says nothing about error behavior, the ID format expected, or auth/permission needs.

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?

Three short paragraphs, front-loaded with the core purpose and then the limit rule. Every sentence carries information; minor verbosity from line wrapping but no wasted prose.

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 no explanation, and the usage limits are covered. But with no annotations and 0% schema description coverage, the critical input format for `str_idxs` is left entirely to the agent to guess, leaving the definition incomplete for correct invocation.

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 0% and both parameters are undocumented. The description never explains what `str_idxs` (a string) should contain or what `limit_one_per_chemsys` does, though the dedup discussion gestures at the chemical-system concept. It fails to compensate for the coverage gap on the required parameter.

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 (complete material information) with batch scope ('for a list of materials'), which distinguishes it from the singular sibling `fetch`. It doesn't explicitly contrast with `search` or `get_phase_diagram_from_elements`, but the batch framing is clear.

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?

Gives an explicit constraint (at most 100 materials) and names the alternative for violating it (`fetch_all` then filter down). This is exactly the when/when-not/alternative structure needed to route the agent.

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