get_material_properties

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

No annotations provided; description must carry burden. Lists output fields (print temperatures, tensile strength, etc.) implying read-only behavior, but does not explicitly state if it has side effects, rate limits, or that it is safe. Minimal behavioral disclosure beyond describing the return content.

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?

Concise and well-structured: brief introductory sentence, bulleted list of output categories, usage guidance, supported materials, and clean parameter docstring. Every sentence adds value with no redundancy.

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 1-parameter tool with no output schema, the description covers purpose, usage, parameter details, and return content. Could briefly mention the structure of the returned property sheet (e.g., JSON object), but overall sufficient for selection and invocation.

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 0% for description, but parameter description adds substantial value: explains material_id is a 'Material key', gives examples, notes case-insensitivity, and lists all supported materials. This fully compensates for schema gaps.

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?

Uses explicit verb 'Get' and specific resource 'full material property sheet', listing detailed categories like thermal specs, mechanical strength. Distinguishes from siblings by focusing on comprehensive property retrieval for unfamiliar materials.

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?

Explicitly states 'Use this before printing with an unfamiliar material or when switching materials' and lists supported materials. Does not mention when not to use or alternatives like compare_material_properties, but context is clear.

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