run_batch_reactor

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

With no annotations, the description carries the full burden. It discloses that the tool simulates over time and updates the lab bench mixture to the final reacted state, indicating a mutation. However, it does not detail side effects, reversibility, or any required permissions. The description adds moderate transparency but lacks depth.

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 two sentences long, efficient, and front-loaded with the main action. Every sentence provides essential information: what it does and why to use it. No redundancy or wasted words.

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 explains the core purpose and effect (updating lab bench state). Since an output schema exists, the lack of explicit output explanation is acceptable. However, the description could briefly mention that results are returned for each time step, but overall it is fairly complete.

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 input schema already provides descriptions for all parameters (name, duration, steps). Since schema description coverage is 0% (meaning the description adds no parameter info), the baseline is 3. The tool description does not explain how parameters are used or add any additional 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?

Description clearly states the tool simulates a Constant Pressure Ideal Gas Batch Reactor, with specific action 'Simulate' and resource 'Batch Reactor', and explains the purpose: to see evolution of temperature and composition, and that it updates lab bench mixture state. This distinguishes it from siblings like equilibrate or compute_ignition_delay.

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 provides usage context ('Use this to see how temperature and composition evolve during combustion or other chemical reactions') but does not specify when not to use it or mention alternative tools. Given the number of sibling simulation tools, more explicit guidance would be beneficial.

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