list_materials

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

There are no annotations, so the description carries the full burden of disclosing behavior. It only says 'list all materials,' implying a read operation, but it does not reveal the return format, whether sub-networks are included, or what happens if the path is invalid. This is minimal disclosure.

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 sentence with no fluff, making it concise and front-loaded. However, it is overly terse, sacrificing necessary detail about parameters and outputs for brevity.

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 simplicity of the tool (1 optional param, no output schema, no annotations), the description is still incomplete. It fails to explain what a 'material' is, what the return value looks like, or what the mat_path parameter expects. The absence of an output schema makes this a notable gap.

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 schema has mat_path with a default of '/mat' and no descriptions. The tool description does not explain mat_path beyond the generic 'material network' context. With schema description coverage at 0%, the description fails to compensate for the missing parameter meaning.

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 'List all materials in a material network' clearly identifies the verb (list) and resource (materials in a material network). It is specific enough to distinguish from get_material_info, which targets a single material, though it does not explicitly mention this distinction.

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?

No guidance is provided about when to use this tool versus alternatives like list_material_types or get_material_info. The description only states what it does, leaving the agent without clear selection criteria.

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