plasticity_list_material_interface_tests

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

Annotations already cover the safety profile (readOnlyHint=true, destructiveHint=false, openWorldHint=false), so the bar is lower. The description still adds two pieces of non-derivable context: the records are 'immutable' and 'caller-attested' (so they are user-supplied provenance, not system-verified), and their results 'are not automatically applied to static FEA or design checks' — a meaningful caveat about downstream effect. It does not discuss pagination or result volume.

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, front-loaded with the verb 'List'; the second sentence carries a distinct caveat rather than repeating the first, so nothing is redundant. The first sentence is heavily adjective-stacked ('immutable caller-attested same-material printed layer-interface') which slows parsing, but the density is domain terminology rather than filler.

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?

A zero-parameter, read-only list tool with no output schema needs the description to characterize the returned records, and it does: identity, setup, failure location, measurement evidence, and scalar/vector traction-separation curves. With annotations covering safety and no parameters to document, this is close to complete; only paging/volume behavior is unaddressed.

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 tool takes zero parameters, which is the baseline-4 case: there is nothing for the description to disambiguate. Schema coverage is 100% but the property set is empty, so the description correctly spends its words on record content rather than parameter semantics.

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 names a specific verb (List) and a well-defined resource (immutable caller-attested same-material printed layer-interface test records), and enumerates the record contents (print-process identity, setup, failure location, traceable measurement evidence, traction-separation curves). This is far more specific than a generic 'list tests' restatement. It stops short of naming the sibling list tools it differs from (list_mmb_mode_i_ii_energy_tests, list_enf_mode_ii_energy_tests, list_dcb_mode_i_energy_tests, list_material_coupon_data), so routing is left to inference.

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 only implied: the verb 'List' plus the record scope tells an agent this is a retrieval tool for previously recorded interface tests. The closing sentence ('Results are not automatically applied to static FEA or design checks') hints at the tool's downstream role but is about result consumption, not about when to pick this tool over match_/analyze_ siblings. No explicit alternatives or prerequisites are stated.

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