list_design_materials

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

With no annotations, the description does the job of disclosing behavior: it returns a compact overview of all materials. It does not mention side effects (none expected for a list operation) but omits details like pagination limits or authentication requirements. The transparency is good but not perfect.

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 two concise sentences with no redundant information. The second sentence provides actionable guidance, making every word earn its place.

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 no input parameters and no output schema, the description is fairly complete: it explains the return content and usage. However, it could mention if there are any limitations (e.g., max number of materials) or whether it includes all material types. Still, it's adequate for a simple list tool.

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?

There are no parameters, so the baseline is 4. The description adds value by documenting the return fields, which substitutes for parameter documentation. No additional parameter meaning 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?

The description clearly states the tool lists all available materials with summary properties, specifying the exact fields returned (name, category, key strengths, weaknesses, best-fit use cases). It also distinguishes from the sibling tool get_material_design_profile, making the purpose unambiguous.

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 explicitly guides when to use this tool ('compare materials at a glance') and when to use an alternative ('before diving deeper with get_material_design_profile'). This provides clear usage context.

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