get_compatible_materials

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

No annotations are provided, so the description carries full burden. It states that the tool returns 'every catalog entry sharing the same material family', which implies a read operation, but does not disclose authentication needs, rate limits, or any side effects. For a safe read tool, more clarity on behavior is expected.

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 three sentences: the first states the purpose, the second explains the return value, and the third clarifies the parameter with examples. No wasted words, and it front-loads the core action.

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 simple lookup tool with one parameter and no output schema, the description gives the essential information. However, it lacks any mention of pagination, sorting, or format of results. Given no annotations, slightly more detail on the output structure would improve 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?

The schema has 0% description coverage, but the description adds concrete examples (e.g., 'pla', 'petg', 'resin') and explains that it is a family name. This provides meaningful semantic context beyond the raw schema, compensating for the lack of schema descriptions.

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 verb 'Find' and the resource 'materials in a given family', with examples of families. It implies a filtering function but does not explicitly contrast with sibling tools like 'list_materials' or 'find_material_substitute', so it loses a point for lack of sibling differentiation.

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 says 'useful for finding compatible substitutes' but provides no explicit guidance on when to use this tool versus alternatives (e.g., find_material_substitute, list_material_catalog). No when-not-to-use or prerequisites are mentioned.

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