lammps_generate_workflow

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It describes the phases and optional shear but does not clarify whether the script is returned as a string or written to output_file, nor any side effects or requirements. The mention of output_file hints at file writing but leaves behavior unclear.

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 well-structured with a concise intro, a numbered phase list, and a clear parameter definition section. Despite listing 21 parameters, it remains readable and front-loads the core purpose without unnecessary verbosity.

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 description covers the multi-phase workflow and all arguments, making it fairly complete for a complex generator. However, it does not explicitly explain the return value or file-writing behavior beyond output_file, and lacks tool-selection context. The existence of an output schema mitigates the return value gap, so a 4 is appropriate.

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%, and the description compensates with a complete Args list that explains all 21 parameters in plain language. It adds conditional context such as 'if NPT' for production_pressure and '0 to skip' for n_minimize_steps, which goes far beyond the schema's type/default information.

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 opens with 'Generate a multi-step LAMMPS workflow (minimize → equilibrate → production)', clearly stating the verb and resource. The three-phase breakdown distinguishes it from sibling tools like lammps_generate_input, which likely handles simpler input generation.

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 clearly implies use for multi-step workflows with its phase list, but it does not explicitly state when to choose this tool over lammps_generate_input or other siblings. No exclusions or alternative recommendations are provided, leaving usage context implicit.

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