plasticity_match_material_interface_test

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

Annotations already declare this a safe read (readOnlyHint=true, destructiveHint=false), but the description adds real context beyond them: the three possible outcomes (no-match, matched, ambiguous), the legacy-record readability limitation, and an explicit disclaimer that a match is experimental evidence only and not a design allowable or analysis pass. That last point is unusually valuable behavioral framing.

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 purpose is front-loaded in the first sentence, and the subsequent sentences each add a distinct fact (return states, legacy limitation, evidence-only caveat). The middle enumeration sentence is dense and long, but given 0% schema coverage that density is largely load-bearing rather than padding.

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 read-only exact-match lookup with no output schema, the definition supplies what an agent needs: the exhaustive identity inputs, the possible return states, the legacy-record caveat, and the scope limitation on what a match means. Nothing material to calling it correctly is missing.

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 description coverage is 0%, so the description must carry the parameter burden, and it does enumerate the identity fields (printer, material, profile, orientation, infill percent/pattern, wall loops, shell layers, nozzle temperature, layer height, test mode, interface normal, load direction, protocol hash). However it only names them in prose; it gives no format semantics (e.g. 64-hex hashes, 3-vector angles), so it partially but not fully compensates for the gap.

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 uses a specific verb ('Find') on a specific resource ('physical layer-interface tests') and immediately constrains it to exact-match semantics, which separates it from the list/record siblings. It never names an alternative tool by name, so an agent still has to infer the boundary against plasticity_list_material_interface_tests and plasticity_match_material_coupon_data.

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?

Usage is implied by 'only for one exact ... match' and by the note that legacy records cannot satisfy an exact match, which tells the agent when this tool will return no-match. There is no explicit statement of when to prefer this over the sibling list, match-coupon, or record tools, so routing guidance is left to inference.

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