move_motor_absolute

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

The description discloses that the motor moves to an absolute position referenced to its last zero, which is useful behavioral context beyond the annotations. However, it does not mention whether the command blocks until the position is reached, how brake/power/timeout affect the movement, or what happens if no zero has been set.

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 concise sentence that front-loads the core action and scope. It contains no filler or redundant restatement of the tool name.

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?

With five parameters, no output schema, and no parameter descriptions, this minimal description is not complete enough for an agent to invoke the tool confidently. Important contextual details such as blocking behavior, the need for a prior zero, how power/brake/timeout are applied, and the return value are missing.

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%, so the description must compensate for all five parameters, but it only loosely maps to 'motor' (port) and 'absolute position' (target_degrees). The optional parameters brake, power, and timeout_seconds are not explained at all, leaving their semantics entirely to the schema titles and defaults.

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 uses a specific verb ('Move') and names the exact resource ('one motor') and the mode ('absolute position relative to its last zero'). It distinguishes itself from the sibling tools move_motor_relative (relative movement) and move_motors_absolute (multiple motors) without extra detail.

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 phrase 'absolute position relative to its last zero' implies that the motor must have a previously established zero reference, and 'one motor' implies single-axis use. However, there is no explicit guidance about when to choose this tool over move_motor_relative or move_motors_absolute, nor any exclusions or prerequisites stated.

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