start_vm

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

The description implies starting a VM but offers no details on behavior: what happens if the VM is already running, whether it waits for startup, any side effects, or required permissions. With no annotations, the description carries the full burden for transparency, which it fails to meet.

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, concise sentence with no wasted words. However, it is under-informative for the critical information it should convey; a bit more detail would not harm conciseness.

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?

Although an output schema exists, the description lacks context about when the VM is considered started, error conditions, or prerequisites. For a tool with one required parameter and no annotations, the description is insufficient for full understanding.

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 has 0% description coverage, and the description does not mention the 'name' parameter or its format. No additional meaning is added beyond the schema definition, leaving parameter semantics completely unspecified.

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 ('Start') and the specific resource ('stopped BSD/Illumos VM'), which distinguishes it from sibling tools like stop_vm and create_vm. It is specific and eliminates ambiguity.

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. The description does not mention prerequisites (e.g., VM must exist and be stopped), nor does it suggest when not to use it (e.g., if VM is already running).

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