convert_vm_to_template

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

Discloses that after conversion the VM cannot be powered on, which is a behavioral trait beyond annotations. The [WRITE] tag and context about irreversible state change add value.

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?

Concise and well-structured: action sentence followed by bullet-point-like args. No wasted words.

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?

Covers purpose, parameter semantics, and key behavioral change. With output schema present, return values need not be described. Lacks error conditions but sufficient for a simple conversion 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?

Schema coverage is 0%, but description adds meaning: vm_name requires powered-off state, and target is an optional target name from config, fully compensating for missing 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?

The description clearly states 'Convert a powered-off VM to a vSphere template' with a specific verb and resource, and distinguishes from sibling tools like deploy_vm_from_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?

Explicitly states prerequisite (VM must be powered off) and references sibling tool deploy_vm_from_template as next step, but doesn't cover when not to use or alternatives beyond that.

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