vehicle_spawn

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

All annotations are false, so the description must cover behavioral traits. The description only says 'spawn' and 'connect,' which implies creation but does not disclose side effects, required permissions, or whether the operation is irreversible. No details about the spawning process or connection are given, making it insufficiently transparent.

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 extremely concise at one sentence, but brevity comes at the cost of informativeness. It is front-loaded but lacks substance. A 3 is appropriate because while it is short, it does not waste words, yet it fails to earn its place by providing necessary detail.

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?

Given the tool's complexity (8 parameters, output schema, sibling tools), the description is highly incomplete. It does not explain the output, the significance of 'connect,' or how parameters interact. The minimal description leaves significant gaps for an AI agent to use the tool correctly.

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 adds no meaning beyond the input schema. While the schema itself describes some parameters (e.g., 'cling' and 'position'), the tool description does not elaborate on them. With 0% schema description coverage from the description, it fails to compensate for the gap, leaving the agent without additional context for parameter usage.

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 states 'Spawn at measured surface plus model-origin clearance and connect.' The verb 'spawn' is clear, and 'vehicle' is implied by the tool name. However, 'connect' is ambiguous and not explained, and it does not differentiate from sibling tools like vehicle_teleport or vehicle_control. The description is partially clear but leaves room for confusion.

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 versus alternatives such as vehicle_teleport or vehicle_remove. There is no mention of prerequisites, context, or exclusions. The description fails to help the agent decide when to invoke this tool.

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