Control simulation

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

With no annotations provided, the description carries the behavioral disclosure burden. It usefully discloses reset semantics ('reloads the current circuit, zeroing time and all state'), but does not explain side effects of run/stop, whether operations block, or what status returns.

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 a single, front-loaded sentence that conveys the primary actions efficiently. The parenthetical detail about external voltage elements is somewhat dense but adds necessary precision without redundancy.

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 omits the 'status' action entirely even though it appears in the schema enum. It also provides no return-value information, no constraints on combining parameters, and no mention of prerequisites, which is significant for a control tool with no output schema and no annotations.

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 low at 33%, and the description partially compensates by explaining extVoltage as an external voltage source element addressed by name. However, the action enum values have no accompanying behavioral descriptions, and maxTimeStep relies on the schema's unit example.

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 identifies the tool's purpose: starting, stopping, resetting the simulation, setting max timestep, and setting external voltage source values. It uses specific verbs and a named resource, though it does not explicitly differentiate itself from siblings like run_transient.

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 explicit guidance on when to use this tool versus alternatives such as run_transient. The action enum implies some usage, but there are no stated conditions, exclusions, or selection criteria.

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