compare_material_properties

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

No annotations are provided, so the description must fully convey behavior. It describes the tool as a read-only comparison that returns insights and guidance. However, it does not disclose any constraints (e.g., validation of material names, error behavior, or whether the comparison is real-time vs cached). The behavioral details are minimal but not misleading.

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 composed of three concise sentences followed by an arg list, all front-loaded with the core purpose. Every sentence serves a distinct role: stating the function, providing usage guidance, and listing what the output highlights. No redundant or unnecessary text.

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 tool's simplicity (2 string parameters, no output schema), the description covers the main aspects: what it does, when to use it, and parameter meaning. It does not describe the return format or pagination, but for a comparison tool that likely returns a human-readable summary, this is acceptable. It could include more detail on expected output structure but is largely complete.

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 input schema only provides titles and types (string) with 0% coverage. The description compensates by naming each parameter and giving example values ('pla', 'petg'), which clarifies that these are material identifiers. This adds valuable context beyond the schema, though it does not specify valid values, case sensitivity, or format.

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 tool performs a side-by-side comparison of two materials covering thermal, mechanical, design limits, and practical guidance. It uses specific verbs ('compare', 'highlights') and identifies the resource (materials). The tool is distinct from siblings like get_material_properties (single material) and compare_print_options (print settings).

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 explicitly advises using this tool when deciding between materials for a project or when switching materials for a reprint, providing concrete examples (PLA vs PETG). While it does not explicitly name alternatives or state when not to use, the context is clear enough for an AI agent to infer appropriate usage relative to sibling tools.

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