vehicle_teleport

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

The description only states the functional goal. It does not disclose side effects, such as whether teleporting resets vehicle dynamics, cancels AI control, or triggers any events. Annotations are all false (unknown), so the description carries full burden but fails to provide behavioral insight.

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 13-word sentence, which is concise and front-loaded. However, it could include more detail without becoming verbose, so it scores a 3.

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 has 4 sub-parameters and an output schema (not shown), but the description does not mention return values, error conditions, or usage context. Preconditions like vehicle existence are omitted. For a mutation command, this is incomplete.

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 description mentions 'position' and 'optional quaternion rotation', which aligns with those parameters in the schema. However, it does not explain the 'reset' parameter or the format of the arrays. Schema coverage is 0% with no parameter descriptions, so the description should compensate but adds minimal value beyond parameter names.

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 'Teleport' and clearly references the resource 'vehicle', along with the action details (position, optional rotation). However, it does not differentiate from sibling tools like 'vehicle_control' which might also affect position, but the teleport nature is distinct enough for a 4.

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 provided on when to use this tool vs alternatives such as vehicle_control or vehicle_ai_configure. Preconditions (e.g., vehicle must exist) and postconditions are not mentioned.

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