reset_simulation

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

No annotations are provided, so the description carries the full behavioral burden. It says the simulation is reset to its initial state, which implies mutation/destruction of current simulation state, but it does not disclose side effects, permission requirements, whether caches or results are cleared, or what happens to existing DOP data.

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 front-loaded, with the core action stated first in one sentence. The Args section is minimal and appropriate for a single required parameter.

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?

For a simulation-state mutation tool with no annotations, no output schema, and numerous simulation-related siblings, the definition is incomplete. It does not cover usage context, side effects, relationship to step_simulation, or state handling, leaving the agent with too little information to call it confidently.

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%, so the description must compensate for the single parameter. It identifies node_path as a 'DOP network node path,' which adds meaningful context beyond the schema title alone, but it still lacks format, expected node type constraints, or examples.

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 specific verb and resource: 'Reset the simulation to its initial state.' This clearly distinguishes reset behavior from sibling tools like step_simulation or get_simulation_info. However, it does not explicitly differentiate itself from all simulation-related siblings or explain what 'initial state' means operationally.

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 no when-to-use guidance, no prerequisites, and no alternatives. It does not tell the agent when resetting is appropriate versus stepping, inspecting, or clearing simulation state.

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