get_materials

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

Annotations already declare 'readOnlyHint: true', 'destructiveHint: false', and 'idempotentHint: true'. The description adds no additional behavioral context, such as pagination behavior, rate limits, or that results are ordered. Given the presence of annotations, the description should at least mention pagination to be helpful.

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 extremely short (4 words) but misses critical information about pagination and return format. Conciseness should not come at the cost of informativeness; a few more words could significantly improve clarity.

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?

No output schema exists, so the description should explain the return value structure (e.g., an array of material objects with pagination metadata). It fails to do so, leaving the agent without enough context to interpret results. The description is incomplete for a paginated list endpoint.

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?

Input schema covers 100% of parameters with descriptions for 'cursor' and 'per_page'. The description does not mention parameters, but schema coverage is high. No additional semantic value beyond schema is provided, which meets the baseline for this dimension.

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 states 'Get all material records' which clearly indicates the action and resource. However, it does not clarify that the tool returns a paginated list (implied by the 'cursor' and 'per_page' parameters) and fails to distinguish itself from sibling tools like 'get_material_group' or 'get_material_groups' beyond the resource name.

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 on when to use this tool versus alternatives. The description does not mention any conditions, prerequisites, or exclusions. For example, it does not indicate that this tool is for listing all materials, while 'get_material' (if it existed) would retrieve a single record.

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