pve_create_vm

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. 'Create a new virtual machine' implies a write operation but reveals nothing about permissions required, whether the VM starts automatically (though 'start' parameter exists), resource allocation limits, error conditions, or what happens on success/failure. For a complex mutation tool with 29 parameters, this is critically inadequate.

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, efficient sentence with zero wasted words. It's appropriately sized for a tool name that already indicates the action ('create_vm'), though it could benefit from more detail given the tool's complexity. Every word earns its place, making it highly concise.

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 high complexity (29 parameters, mutation operation, no output schema, and no annotations), the description is severely incomplete. It doesn't address behavioral aspects, usage context, or output expectations. While the schema covers parameters well, the description fails to provide the necessary context for safe and effective use of this significant system operation.

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 description coverage is 100%, meaning all 29 parameters are documented in the schema itself. The description adds no parameter-specific information beyond the generic 'create' action. According to scoring rules, with high schema coverage (>80%), the baseline is 3 even with no param info in the description. The description doesn't compensate but doesn't need to given the schema's completeness.

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 'Create a new virtual machine' clearly states the action (create) and resource (virtual machine), which is specific and unambiguous. However, it doesn't differentiate this tool from other VM-related creation tools like pve_create_container or pve_clone_vm, which are also in the sibling list. The purpose is clear but lacks sibling differentiation.

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 provides no guidance on when to use this tool versus alternatives. There are multiple sibling tools for creating VMs (e.g., pve_clone_vm, pve_create_container) and related operations (e.g., pve_start_vm, pve_update_vm_config), but the description offers no context, prerequisites, or exclusions. This leaves the agent with no usage guidance.

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