vm_clone

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

No annotations provided. The description includes a '[WRITE][risk=medium]' tag indicating it's a write operation with medium risk, adding some transparency. No contradiction with annotations (none). Lacks details on side effects or prerequisites.

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 concise, front-loaded with risk and purpose, and uses a docstring format for args. Every sentence adds information.

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?

The tool has low complexity (3 params, no output schema). Description covers purpose, args, and risk, but lacks return value info and preconditions (e.g., source VM state). Missing context for a clone 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 coverage is 0%, so the description compensates by explaining each parameter's meaning: vm_ext_id as source from vm_list, new_name as clone name, target with omission default. This adds value beyond the schema.

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 it clones a VM to a new name, with a specific verb and resource. It includes a risk tag. However, it does not differentiate from sibling tools like vm_create or vm_migrate.

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 explains argument roles and default behavior for 'target', but does not provide guidance on when to use this tool versus alternatives (e.g., vm_create). No when-not-to-use conditions.

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