Drive

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

With only readOnlyHint=false and openWorldHint=false in annotations, the description carries the load and does so well: it discloses the side effects of disabling autopilot and starting the simulation, that the rover stops on collisions, concrete speed/turn rates, and that wait=true yields the post-move observation. These are exactly the behavioral facts an agent needs before mutating world state.

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?

Front-loaded with the core action and direction enum, then side effects, then timing math, then return behavior. Dense but every sentence carries operational value; nothing is redundant with the schema.

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 mutating, single-step motion tool with no output schema and minimal annotations, the description covers action, units, side effects, collision termination, and return semantics. Only the relationship to the sibling 'turn' tool is unaddressed.

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 67% (wait and seconds documented; direction is an enum without prose), and the description adds real semantics: 2 rad/s so 90 degrees takes about 0.8 s, forward at 65% of max (approx 61 px/s), backward approx 51 px/s, and what wait=true returns. That lets an agent choose 'seconds' intelligently rather than guess.

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?

States a specific verb and resource ('Move the rover') plus the direction set and that turns are in place, which separates it from generic motion. It never mentions the sibling tool 'turn', so an agent cannot tell from the description alone why it would pick one over the other.

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?

It provides implied usage context: turns autopilot off and starts the simulation, and wait=true returns the observation after the move. But there is no explicit when-to-use vs 'turn', 'run_program', or 'set_autopilot', and no guidance on when to set wait=false.

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