move_servos

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

With no annotations, the description carries the full burden and does well: it discloses that the call waits until arrival, that positions are clamped to channel limits, and that channels are turned on if off. It does not mention error handling or permission requirements, but the core behavioral traits are covered.

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?

Three short sentences, front-loaded with the primary action and followed by essential parameter details. Every sentence earns its place with no filler.

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?

The description explains the nested positions object, the blocking wait, clamping, and power-on side effect. For a tool with no output schema and no annotations, this is nearly complete. Minor gaps include error behavior for unknown channels and confirmation of the default duration.

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 coverage is 0%, but the description compensates by explaining the nested positions object format, giving an example, and clarifying duration_s semantics (0 means each channel's own speed). It does not mention the default duration of 1, but otherwise adds substantial meaning beyond 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?

The description states a specific verb and resource: 'Move one or more servos and wait until they arrive.' It is clear what the tool does, though it does not explicitly distinguish itself from siblings like go_to_pose or play_sequence.

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?

Usage is implied by describing the blocking wait and the effect of turning channels on. However, there is no explicit guidance on when to use this tool versus go_to_pose, play_sequence, or stop_all, nor any stated preconditions.

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