convert_vm_to_template

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

Discloses irreversibility, which is critical, but with no annotations, the description must cover more. It does not mention other behavioral traits like whether the VM must be stopped, permissions needed, or side effects.

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?

Extremely concise: a single sentence and a named list of parameters. No wasted words, and the irreversibility note is front-loaded.

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 simple tool with two parameters and an output schema, the description is adequate but misses important context like the requirement for the VM to be stopped, which is typical for such an 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?

Input schema has 0% coverage with descriptions, and the description only lists parameter names in an 'Args' section without adding meaning or constraints beyond the schema, failing to compensate for the lack of schema descriptions.

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?

Clearly states the action (convert), the resource (VM), and the result (template), with the key qualifier 'irreversible'. Distinguishes from sibling tools like clone_vm and convert_container_to_template.

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?

Implies usage via the action description but provides no explicit guidance on when to use this tool versus alternatives, prerequisites (e.g., VM state), or context for the irreversible operation.

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