movel_y

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

No annotations are provided. The description only says it moves the TCP along Y; it does not disclose any behavioral traits like blocking nature, error handling, timeouts, or required robot state.

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 very short (two lines) and gets to the point. It could be improved by front-loading the action, but it is concise without wasted words.

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?

Given no output schema and simple parameters, the description lacks information on return values, error handling, or prerequisites. It is incomplete for a command that likely requires a connected robot.

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%, but the description adds meaning by explaining ip as robot address and distance as movement distance in meters. However, it lacks details like allowed ranges or format.

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 states the tool moves the robot's TCP along the Y-axis, specifying the parameters IP and distance in meters. It distinguishes from sibling tools like movel_x and movel_z.

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 does not provide guidance on when to use this tool vs alternatives such as movel, movel_x, or movel_z. There is no mention of prerequisites or context.

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