zero_position

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

With no annotations, the description carries the behavioral burden. It explicitly states that the command redefines the current position without moving the shaft and mentions that broadcasts receive no responses. It does not discuss persistence or side effects on homing/limits, but for this simple command it is reasonably transparent.

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 compact and front-loaded, with the core purpose stated first. The firmware reference, no-movement clarification, return note, and parameter semantics are each useful and earn their place.

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 single-parameter command with no output schema, the description covers purpose, side effects, response confirmation, and parameter input variants. It is slightly light on exact response format and persistence of the zero reference, but those are not critical for invoking this tool.

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 only says 'motor' is a required string, but the description explains that it accepts a numeric alias, a 16-hex-character ID, or 'all', and discloses that broadcasting to all motors yields no responses. This significantly adds meaning beyond the bare 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 uses a specific verb and resource: 'Make the current position the position zero' and 'Redefines the current shaft location as 0 degrees.' It clearly distinguishes this calibration action from movement commands by explicitly noting that no physical movement occurs.

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 implies the primary use case—setting the current position as the origin—and the 'no movement' note helps avoid confusion with move commands. However, it does not explicitly state when to prefer this over alternatives like homing, nor does it mention prerequisites or cautionary conditions.

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