get_material_properties

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

No annotations provided. Description states it 'returns' multiple property sets, implying a read operation with no side effects, but does not explicitly confirm read-only behavior, disclose rate limits, or discuss response size.

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?

Two sentences: first defines purpose and scope, second lists allowed material identifiers. Actionable, no filler, front-loaded.

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?

Covers what the tool returns (property groups) and valid inputs (materials). Lacks output schema or return format description, but for a straightforward lookup this is acceptable. The list of materials compensates for missing enum constraints.

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 covers both parameters (material, properties) with descriptions. The description adds concrete list of 20 available materials and 5 property group names, enriching the schema's examples and helping the agent form valid queries.

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?

Clearly states 'Look up material properties for injection molding simulation' and enumerates specific property groups (Cross-WLF viscosity, 2-domain Tait PVT, etc.). Distinct from sibling tools like compare_materials or validate_process_parameters.

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?

Provides list of available materials, which helps choosing valid inputs, but lacks explicit when-to-use/not-use guidance or comparisons with alternatives. Use is implied but not directed.

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