Fetch All

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

With no annotations, the description carries the full burden. It discloses the return contents (id, title, robocrys description, URL, metadata) and hedges with 'as available,' implying possibly incomplete data, but says nothing about result size, cost, or pagination behavior for a full-corpus fetch — a notable omission for a bulk operation.

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?

Purpose is front-loaded in a single sentence, followed by a structured returns block. The returns section is a bit awkwardly formatted for content already covered by the output schema, but nothing is egregiously wasteful.

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, yet the description usefully summarizes them anyway. Combined with a zero-parameter interface and no annotations, the definition is nearly self-sufficient, missing only bulk-vs-targeted usage guidance.

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?

The tool takes zero parameters and the schema is empty, so there is nothing for the description to clarify; baseline of 4 applies. No parameter guidance is needed.

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 for the entire Materials Project'), with the scope word 'entire' signaling a bulk operation. That implicitly sets it apart from the single-item 'fetch' and subset 'fetch_many' siblings, though neither is named 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 statement of when to use this tool versus fetch, fetch_many, or search, and no conditions or exclusions given. The agent must infer that 'entire Materials Project' means a full-corpus bulk read rather than a targeted lookup.

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