create_vm

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

With no annotations, the description must disclose behavioral traits fully. It lists parameters and defaults but does not mention side effects (e.g., resource allocation, potential conflicts with existing VM IDs, or required permissions). The behavior beyond parameter input is largely opaque.

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 structured as a clear list of arguments with inline explanations, making it easy to scan. However, it is lengthy and could be more concise by grouping related parameters. It is front-loaded with the purpose.

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 description adequately covers parameter semantics given the tool's complexity and the existence of an output schema. However, it lacks information on error handling, return values, or prerequisites like storage availability, which limits completeness for a 22-parameter tool.

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, meaning all parameter meaning comes from the tool description. The description explains each parameter with examples and default values (e.g., 'scsi0: First SCSI disk (e.g. "local-lvm:32")'), adding substantial value beyond schema field names and types.

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 begins with 'Create a new QEMU virtual machine,' which is a specific verb+resource. Among sibling tools like clone_vm and create_container, this tool is clearly distinguished as the primary VM creation function.

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 explicit guidance is provided on when to use create_vm versus alternatives like clone_vm or create_container. There is no discussion of prerequisites, such as available node capacity or storage, nor any 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.