Restart an ABB robot controller via RWS in warm or cold mode; warm start resets RAPID, cold performs a full restart.
Restart the robot controller via RWS (warm-start, resets RAPID)
| Name | Required | Description | Default |
|---|---|---|---|
| mode | No | Restart mode: warm (keep system params) or cold (full restart). Default: warm. |
Changes observed during successful MCP inspections.
v3.1.0Does 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 discloses that RAPID is reset, but omits downtime, safety implications, required mastership/auth, and what happens to running programs, and its 'warm-start' parenthetical is incomplete because the schema also allows cold restarts.
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 with no waste. The purpose and main effect are stated immediately.
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 high-impact controller restart with no annotations and no output schema, the description is too sparse. It should disclose disruption, requirements, and how the optional cold mode differs from the stated warm-start behavior.
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 100%, and the schema fully documents the optional mode enum including warm vs cold behavior. The description adds no further parameter detail beyond mentioning warm-start, so baseline 3 is appropriate.
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 verb and resource: restart the robot controller via RWS, and adds the key effect of resetting RAPID. It is distinguishable from siblings such as rws_reset_pp, though it does not explicitly contrast with them.
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?
No when-to-use guidance, prerequisites, exclusions, or alternatives are provided. The agent must infer that this tool is for controller restarts rather than program pointer resets or program stops.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.