move_forward

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It does not mention whether the robot stops automatically after the duration, whether the command blocks or is asynchronous, or any prerequisites like a connected device. This is a significant gap for a movement control tool.

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, well-structured sentence that is front-loaded and contains no filler. It efficiently communicates the core purpose without unnecessary words.

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 tool is simple, the schema covers both parameters, and an output schema exists, so the description does not need to explain return values. However, the lack of behavioral disclaimers and usage guidance prevents a perfect score, though it is still adequate for basic invocation.

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 input schema already fully describes both parameters (speed_pct and duration_s) with details about clamping and defaults. The description adds no additional parameter-specific meaning beyond restating 'speed percent' and 'timed duration', so the baseline of 3 applies.

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 the action: drive the EV3 tank motors forward for a timed duration at a given speed percent. It uses a specific verb and resource, and the sibling names (move_backward, turn_left, etc.) make it unambiguous which tool is being described.

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 when to use this tool (to move forward) but provides no explicit guidance about when not to use it or which alternative to choose (e.g., move_backward for reverse). It lacks the explicit alternatives or exclusions seen in higher-scoring descriptions.

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