pve_convert_vm_to_template

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

With no annotations provided, the description carries full burden for behavioral disclosure. 'Convert VM to template' implies a destructive or transformative operation, but provides no information about whether this is reversible, what permissions are required, whether the VM becomes unusable after conversion, or what happens to running instances. For a tool that likely permanently alters VM state, this lack of behavioral context 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 maximally concise at just three words, with zero wasted language. It's front-loaded with the core action and doesn't contain any unnecessary elaboration. While this conciseness comes at the expense of completeness, the description itself is structurally efficient.

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 tool that performs a potentially destructive VM transformation with no annotations and no output schema, the description is completely inadequate. It fails to explain what 'converting to template' means operationally, what the implications are, what permissions are required, or what the result looks like. The agent would struggle to use this tool correctly without significant external knowledge.

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 100% description coverage, with all three parameters clearly documented in the schema itself. The description adds no additional parameter information beyond what's already in the structured schema. According to scoring rules, when schema_description_coverage is high (>80%), the baseline is 3 even with no param info in the description, which applies here.

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 'Convert VM to template' is essentially a tautology that restates the tool name with minimal elaboration. It specifies the verb ('Convert') and resource ('VM to template'), but provides no additional context about what this operation entails or how it differs from similar operations. Compared to sibling tools like 'pve_clone_vm' or 'pve_create_vm_snapshot', there's no differentiation in purpose or scope.

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 absolutely no guidance on when to use this tool versus alternatives. There are no mentions of prerequisites, timing considerations, or comparisons to related tools like 'pve_convert_container_to_template' or 'pve_create_vm_snapshot'. The agent receives no help in determining appropriate use cases for this conversion operation.

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