Test joint range by sweeping every driven joint through its full range for a set number of steps, returning travel statistics to verify motion and detect limits.
Sweep every driven joint through its range for n steps; return travel stats.
| Name | Required | Description | Default |
|---|---|---|---|
| n | No |
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden of behavioral disclosure. It states that joints are swept and stats are returned, but does not clarify whether simulation state is modified, whether the motion is reversible, or what permissions or constraints apply.
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?
A single, front-loaded sentence with no redundant or filler content. It delivers the core action and scope 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?
An output schema exists, so return values need not be explained further. However, with no annotations and several similar siblings, the description leaves key context unaddressed: side effects on simulation state and why an agent should pick this over sim_sweep or sim_range_test.
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 schema provides no description for the sole parameter 'n', so the description must compensate. It adds meaning by saying 'for n steps,' but gives no range, format, or constraints beyond the default already in the schema.
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 ('Sweep') and a clear resource scope ('every driven joint through its range for n steps'). This distinguishes it from single-joint or step tools, but it does not explicitly differentiate from close siblings like sim_sweep or sim_range_test.
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 guidance is given on when to choose this over sim_sweep, sim_range_test, or sim_step. The implied usage is clear from the verb, but there are no conditions or alternatives mentioned.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.