list_materials

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

With no annotations, the description carries full burden. It provides behavioral context: readonly (tier: readonly-owner), pagination via cursor, up to 1000 records per page, and filtering. However, it does not describe error handling, rate limits, or what happens on invalid filters. The 'Required on create' statement is confusing.

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 short and includes a mapping to the REST endpoint and a tier tag. However, the phrase 'Required on create: name records' is unclear and reduces efficiency. Overall, it is concise but could be clearer.

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 tool has two parameters, full schema coverage, and no output schema. Description covers pagination and filtering but does not explain the return structure or fields. The confusing 'Required on create' part does not add value, leaving gaps in completeness.

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 coverage is 100%; both parameters are documented in the input schema. The description adds minimal extra meaning: it mentions 'optionally filtered', but not cursor or details. Baseline score of 3 is appropriate.

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 catalog materials, products, or labor rates, distinguishing it from siblings like get_material (single item) and list_job_materials (job-specific). The phrase 'Required on create: name records' is ambiguous, but the overall purpose is clear.

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 for listing catalog items via the resource listing, but does not explicitly state when to use this tool versus alternatives like get_material or list_job_materials. No when-not or exclusion criteria are provided.

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