set_simulationStart or pause the robot's physics simulation by setting running to true or false, enabling controlled observation and testing of simulator behavior.
Start (running=true) or pause (running=false) the physics simulation.
| Name | Required | Description | Default |
|---|---|---|---|
| running | Yes |
Changes observed during successful MCP inspections.
v1.1.1Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The annotations only declare idempotentHint=true; the description adds state-setting semantics consistent with that hint. However, it does not disclose whether pausing preserves simulation state, whether the simulator must already be open, or what side effects occur.
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 one compact sentence that front-loads both modes and maps the parameter value directly. Every clause earns its place.
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 one-parameter toggle with no output schema, the description covers the core invocation semantics well. It is slightly incomplete because it omits whether the simulator must be open and what happens to simulation state while paused.
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 single boolean parameter has 0% schema description coverage, but the description fully defines its meaning: true starts and false pauses the simulation. No further parameter semantics are missing.
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 states a specific action (start/pause), resource (physics simulation), and the two modes controlled by the parameter. It clearly distinguishes this state toggle from siblings like open_simulator and stop.
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?
It provides the running=true/false mapping, which implies how to use the tool, but does not explain when to choose this over open_simulator, stop, or other simulation-control siblings. No preconditions or exclusions are stated.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.