vsphere_clone_vm

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

Discloses important behavioral traits: cloning copies every disk (hence slow), defaults to source placement, async behavior with wait parameter, and requires write permission. This goes well beyond the minimal annotations (all false) and gives the agent critical execution expectations.

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?

Front-loaded with purpose, then key behavioral notes, then a well-organized parameter list. The length is justified by the tool's complexity; each sentence adds value. Could be slightly tightened, but structure is clear.

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?

With 10 parameters, sparse annotations, and an output schema (present but not shown), the description covers all essential aspects: operation type, placement defaults, performance implications, async patterns, permission requirements, per-parameter meaning, and references the companion task-polling 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?

The Args block provides meaningful descriptions for all 10 parameters, including the accepted forms for 'vm' (name, moid, UUID, or inventory path) and the purpose of each placement override. Since the input schema has no descriptions (0% coverage), this fully compensates.

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 opens with a specific verb-resource pair: 'Clone a virtual machine or deploy one from a template.' This clearly defines the action and distinguishes it from sibling tools like vsphere_migrate_vm, vsphere_reconfigure_vm, and vsphere_delete_vm.

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?

Provides clear usage context: explains placement defaults and how to override them, warns about long clone times, and gives explicit guidance on using wait=false to get a task ID and poll with vsphere_get_task. However, it does not explicitly mention when to prefer cloning over alternatives like vsphere_migrate_vm, though this is inferable.

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