cst_list_materials

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

Description indicates return content (name, properties, usage notes) but does not explicitly state it is a read-only operation with no side effects. Given no annotations, provides moderate transparency but could clarify data source or performance.

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?

Extremely concise two-sentence structure. Front-loaded with core purpose, then adds filtering and return details. No unnecessary 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?

For a list tool without output schema, description specifies return content (name, properties, notes). Lacks pagination or size hints but sufficient for typical use.

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 already fully describes the parameter with enum values. Description adds context by identifying the categories as material types, but no additional syntax or usage details beyond schema. Baseline 3 due to 100% schema coverage.

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?

Clearly states it lists available materials from a specific bundled database, with optional filtering by category. Distinguishes itself from sibling tools like cst_get_material_info (single material info) and cst_create_material (creation).

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?

Provides filtering options but no explicit guidance on when to use this versus sibling tools like cst_get_material_info or cst_list_ferrite_materials for specific material types.

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