plasticity_list_dcb_mode_i_energy_tests

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

Annotations already declare readOnlyHint/destructiveHint, so safety is covered. The description adds real value beyond that: records are immutable, output is summarized rather than full, and the data is explicitly not fed into cohesive FEA — a meaningful behavioral boundary.

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?

Three short sentences, front-loaded with the core purpose followed by the routing hint and the scope caveat. No 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?

No output schema, but the description conveys what is returned (compact summaries versus full observations in the read sibling). Combined with the scope exclusions, an agent has enough to call it correctly; only exact summary fields are unspecified.

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, so there is nothing for the description to disambiguate; baseline is set at 4. No parameter guidance is needed or missing.

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?

States a precise verb (List) and resource (immutable physical DCB Mode-I energy records), plus the return shape ('compact summaries'). This clearly distinguishes it from plasticity_read_dcb_mode_i_energy_test, which returns full observations.

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 routes the agent: use this to list, use plasticity_read_dcb_mode_i_energy_test to retrieve full measured observations and MBT results for a selected record. It also clarifies the domain scope (separate from traction-separation data, not applied to cohesive FEA).

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