Clone guest

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

Explains the 'full' parameter (full vs. linked clone) but omits other behavioral traits like prerequisites, side effects (e.g., resource usage), or whether the source must be powered off. No annotations provided.

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 at two sentences, front-loaded with action. 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?

No output schema, yet description fails to mention what the tool returns (e.g., new VMID or status). Does not cover important operational context like resource requirements or potential conflicts.

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 description coverage is 100%, so baseline 3. The description adds context for the 'full' parameter but does not enhance meaning for other parameters (guest, newid, name, target).

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?

Description clearly states the verb 'Clone' and resource 'VM or container'. It highlights deployment from a template, distinguishing it from sibling tools like backup_guest or migrate_guest.

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?

Indicates good use case ('deploying from a template') but lacks explicit when-not-to-use or alternatives. Sibling tools exist for backup or migration, but no exclusion guidance.

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