drive_backward

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

No annotations are provided, so the description must carry the transparency burden. It adds context about using the position controller for accurate movement, which is useful, but it does not disclose behaviors such as blocking until completion, error conditions, or what happens if the robot encounters an obstacle.

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?

Two concise sentences, front-loaded with the primary action, and a secondary clause explaining the movement method. No redundant wording.

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?

Simple tool with a clear purpose and full schema coverage. The description plus schema sufficiently explain the tool for a simple distance-based movement, though it lacks warnings about physical movement or connection prerequisites. Given the output schema exists, this is reasonably complete.

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 100%, with both 'distance' and 'speed' already described. The description repeats that distance is in meters but adds no additional parameter semantics 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 clearly states 'Drive backward a specified distance in meters', specifying the verb (drive), direction (backward), and metric (distance in meters). This distinguishes it from siblings like drive_forward and pivot.

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 second sentence 'Uses RVR's internal position controller for accurate movement' implies use when precise distance control is needed, but it does not explicitly mention alternatives or when not to use this tool. Guidance is implied rather than explicit.

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