list_materials

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

Annotations already declare readOnlyHint=true, openWorldHint=true, idempotentHint=true, and destructiveHint=false, covering the safety profile. The description adds context about the catalog scope and sample fields, but does not disclose other behavioral traits like ordering, pagination, or update frequency. This is adequate but minimal for a simple list tool.

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?

The description is a single, well-structured sentence that front-loads the action ('List materials/chemicals') and includes the key context ('Fieldwork catalog'). No wasted words.

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?

Given the tool's simplicity (no parameters), strong annotations, and presence of an output schema, the description is complete. It names the specific resource and gives example return fields, which is sufficient for an agent to understand what the tool does.

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 has zero parameters, so schema coverage is complete. Per rubric, the baseline is 4 when there are no parameters, and the description does not need to explain parameters. The description's mention of 'name, EPA #, etc.' hints at return fields but does not affect parameter semantics.

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 ('List') and resource ('materials/chemicals in the Fieldwork catalog') with example fields (name, EPA #). It is clear and unambiguous, but it does not explicitly distinguish itself from sibling tools like 'what_products_do_we_carry', which could overlap in purpose.

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?

The description implies usage: use when you need to see materials/chemicals in the catalog. However, it provides no explicit guidance on when not to use it or alternatives, such as the similar-sounding 'what_products_do_we_carry'.

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