vm_create

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

The description discloses key behaviors: creates a powered-off VM, fails before creation if datastore not found, and audit logging. Annotations provide readOnlyHint=false and destructiveHint=false, which align. The description adds context about failure and auditing but could mention other side effects like resource consumption.

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 well-structured with a leading summary, detailed behavior, Args section, and Returns. Every sentence adds value, no redundancy. It is concise yet comprehensive.

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 complexity (8 params, many sibling tools, output schema present), the description covers all necessary aspects: purpose, usage, parameters, behavior, and error conditions. It is complete without reliance on output schema details.

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 provides detailed explanations for all 8 parameters, including defaults, constraints (vm_name must not exist), and advice on omitting optional parameters. With schema coverage at 0%, this is essential and adds significant meaning beyond the input schema.

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 creates an empty VM with specific hardware sizing, and distinguishes it from related tools like deploy_vm_from_ova and vm_clone. The verb 'Create' and the resource 'empty VM' are specific, and it differentiates from sibling tools.

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?

The description explicitly states when to use this tool: to create a blank VM for manual setup, and when to use alternatives (attach_iso_to_vm, deploy_vm_from_ova, deploy_vm_from_template, vm_clone) for ready-to-run guests. This provides clear guidance on tool selection.

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