move_motors_absolute

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

Annotations already provide readOnlyHint=false and destructiveHint=false, so the agent knows this is a mutating, non-destructive operation. The description adds the concurrent-execution trait, which is useful, but it does not disclose timeout handling, brake behavior, blocking semantics, or what happens if a motor fails partway.

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 filler. Every word contributes to identifying the core action and distinguishing scope, making it appropriately concise.

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 tool with five parameters, three required, zero schema descriptions, and no output schema, this one-sentence description is underpowered. An agent still lacks critical invocation details such as how the ports/powers/target_degrees arrays must align, what units are expected, and what the tool returns or does on timeout, so the description is not complete enough for reliable use.

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 carries the burden for parameter meaning. It only faintly maps 'absolute positions' to target_degrees and 'several motors' to ports; it never clarifies array correspondence, power units, port enumeration, or timeout/brake effects. The property names are self-descriptive, but the description adds almost no semantic value beyond them.

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 action ('Move') and resource ('several motors'), and the qualifier 'concurrently to independent absolute positions' clearly distinguishes it from singular or relative motion siblings like move_motor_absolute and move_motors_relative. An agent can tell what this tool does without opening the schema.

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 conveys clear usage context: when multiple motors need to be moved at once to absolute positions. It does not explicitly state exclusions such as 'for a single motor use move_motor_absolute' or 'for relative motion use move_motors_relative,' but the phrasing implies the appropriate selection among the sibling tools.

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