vector_drive_off_charger

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

With no annotations provided, the description carries the full responsibility for behavioral disclosure. It does not state whether the robot physically moves, whether the command can fail (e.g., if not on charger), or any safety considerations. This is a minimal action description with no added behavioral context.

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?

A single, perfectly front-loaded sentence with zero wasted words. Every element contributes to meaning.

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 parameterless command with no output schema, the description is nearly complete—it states the exact action. However, the lack of any usage guidance or non-obvious prerequisites (e.g., must be on charger for this to make sense) leaves a small gap for an agent deciding whether to call it.

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 tool has zero parameters and schema coverage is 100%, so the baseline for 0 params is 4. The description doesn't need to explain parameter meanings because none exist, and it adds no confusion.

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 'Drive the robot off its charger' uses a specific verb and resource, clearly distinguishing it from the sibling vector_drive_on_charger and other movement commands. An agent can immediately identify the tool's purpose without needing to inspect siblings.

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?

No guidance is given on when to use this tool versus alternatives, such as when the robot must already be on the charger or how it relates to vector_drive_on_charger. The expected usage context is implied by the name but never stated, leaving the agent to infer prerequisites.

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