fulfillment_materials

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

With no annotations, the description fully discloses behavior: it describes the search matching (word-boundary, case-insensitive), technology filter behavior, limit default, and authentication requirements for direct mode. No contradictions.

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 well-structured with paragraphs and a bulleted Args section. While detailed, it could be slightly more concise, but every sentence adds value.

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?

The description explains the return format (materials with technology, color, finish, pricing) and mentions catalog size. It covers filtering and defaults adequately. No output schema exists, so this is sufficient; minor omission of pagination details.

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 0%, but the description adds detailed semantics for all three parameters: search includes examples and matching behavior, technology lists common values and matching scope, and limit specifies default. This compensates fully.

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 clearly states it lists available materials from external manufacturing services, specifies the returned fields, and distinguishes itself from sibling tools like fulfillment_quote by referencing the use of the material id for quoting.

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?

It explains when to use the tool (to list materials), advises using filters to narrow results, and mentions authentication modes. However, it lacks explicit guidance on when not to use this tool or direct comparisons to alternatives.

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