lammps_parse_thermo

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

With no annotations, the description bears the full burden of disclosing behavioral traits. It only says 'return time-series data' without explaining the exact output structure, how malformed files are handled, or whether data is sorted. This leaves significant ambiguity for an agent invoking the tool.

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 brief and front-loaded with the action verb. It lists example columns for added context, and the 'Args' section is a minor redundancy but not wasteful. Every sentence contributes to understanding the tool's purpose.

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?

Given the tool's simplicity (one parameter, output schema present), the description covers the essential action and input. It could mention how the returned time-series data is structured or how it differs from dump parsing, but the output schema likely fills that role. Overall it is adequate for a focused parser tool.

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 provides zero description coverage, but the description compensates by defining 'filepath' as 'Path to the LAMMPS thermo output file.' This gives the agent clear meaning for the only parameter, though it lacks details like supporting wildcards or relative/absolute paths.

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 function: parsing LAMMPS thermodynamic output and returning time-series data. It specifies the resource (log/thermo.dat files) and gives concrete column examples, distinguishing it from sibling tools like lammps_parse_dump which handles dump files.

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 by mentioning the input file types, but it does not explicitly state when to prefer this tool over alternatives such as lammps_parse_dump or lammps_file_summary. There are no exclusions or prerequisite conditions mentioned.

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