start_vm

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

The description only says 'starts', implying a state change. It does not disclose whether the operation is synchronous, what happens if the VM is already running, error scenarios, or required permissions. No annotations are provided to fill these gaps.

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, front-loaded sentence that conveys the essential purpose. It is concise, though it could include minor clarifying details without harm.

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 state-changing tool with no output schema and no annotations, the description is too minimal. It lacks details on behavior (e.g., async vs sync), return value, error handling, or prerequisites. More context is needed for an AI agent to use it 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?

Schema coverage is 100%, so the schema already describes all parameters (node, type, vmid). The description adds no additional semantic meaning beyond the schema, earning a baseline score of 3.

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 tool's action: 'Starts a QEMU VM or an LXC container'. It uses a specific verb ('starts') and resource type ('VM' or 'container'), distinguishing it from siblings like stop_vm, shutdown_vm, and destroy_vm.

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 on when to use this tool versus alternatives such as reboot_vm or shutdown_vm. Prerequisites (e.g., VM must be stopped before starting) are not mentioned, and there is no mention of when not to use it.

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