deploy_linked_clone

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

Discloses write nature ([WRITE]), near-instant characteristics, dependency on source VM, and audit trail. Annotations confirm readOnlyHint=false, no contradictions. Could mention consequences if source VM is deleted, but overall good.

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?

Well-structured with summary, detailed explanation, Args list, and Returns. Efficient but slightly long; however, every sentence adds value.

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 cloning process, dependencies, alternatives, parameter details, and return values. Output schema exists but description also explains return. No gaps for an 8-parameter 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 has 0% description coverage, but the 'Args' section explains each parameter's purpose, constraints, and defaults, adding significant meaning beyond the schema titles. For example, 'target: vCenter/ESXi target name from config.yaml'.

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 'Create a linked clone from a VM snapshot' and contrasts with siblings: 'use vm_clone or deploy_vm_from_template for fully independent copies'. The verb and resource are specific.

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 when to use ('fastest provisioning method for test/dev fleets') and when not ('for fully independent copies'). Provides prerequisite: 'Requires the source VM to have the named snapshot — run vm_list_snapshots first'.

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