simulation_start

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

With no annotations provided, the description carries the full burden, and it does disclose one genuinely useful behavior: start is asynchronous and returns immediately. However, it says nothing about idempotency (what happens if already started), required permissions, or error conditions, which leaves significant gaps for a state-changing 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?

Two short sentences with the action stated first and the asynchronous caveat immediately after. Every clause carries information; there is no padding.

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 state-mutating simulation control tool with zero annotation coverage, no output schema, and four undocumented parameters, the description is too thin. The async note is valuable but does not compensate for the missing parameter semantics and lifecycle preconditions.

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% across four parameters (end_time, work_dir, model_root, statistics_start), and the description mentions none of them. Even basic meaning such as the time units for end_time or what statistics_start controls is absent, so an agent cannot populate optional parameters with confidence.

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 uses a specific verb and resource ('Start the EventController'), making the core action unambiguous. It does not differentiate itself from sibling tools such as simulation_run or simulation_reset, so an agent must infer the distinction from names alone.

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?

There is no guidance on when to use this versus simulation_run, simulation_reset, or simulation_stop, nor any stated prerequisites (e.g., whether a model must be open first). Usage is only implied by the name and the word 'Start'.

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