lammps_identify_plastic_events

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states what the tool does but not how the threshold is applied (e.g., particles with D²min above threshold are identified as plastic events). No side effects, output format, or edge-case behavior is disclosed.

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 description is extremely concise, with a one-sentence purpose statement and a clear 'Args' section listing the two parameters. Every word earns its place 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?

The tool is simple with only two parameters and has an output schema, so the description doesn't need to detail return values. However, it lacks context about how this fits into a LAMMPS workflow (e.g., that it follows lammps_d2min) and what ‘plastic rearrangement’ means in practice, leaving minor gaps.

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 schema has no descriptions on its properties (0% coverage), and the description partially compensates by explaining d2min_json as 'JSON string with D²min values for each particle' and threshold as 'D²min threshold for plastic events.' The threshold explanation is somewhat tautological, but it does add meaning beyond the schema.

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 clearly states the tool's purpose: 'Identify particles that underwent plastic rearrangement.' This is a specific verb+resource combination that distinguishes it from sibling tools like lammps_parse_dump or lammps_nematic_order.

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?

The description implies usage through the parameter d2min_json, suggesting it consumes output from a D²min calculation, but it does not explicitly state when to use this tool versus alternatives or provide any exclusion criteria.

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