deploy_vm_from_ova

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

Discloses upload time scaling with OVA size, failure behavior before resource creation, and audit logging. Annotations already indicate non-read-only; description adds valuable context beyond annotations.

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?

Description is thorough but not overly verbose; the 'Args' section is well-structured. A minor reduction in explanation length could improve conciseness, but every sentence serves a purpose.

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, usage, behavior, all parameters, return value, and references to config.yaml. Even with an output schema, the description provides complete context for the tool's 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 description fully compensates by explaining all 8 parameters with constraints (e.g., local path must be readable, vm_name must not exist, defaults for optional params).

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 it creates a VM by importing a local .ova file, using 'Create' as the verb and specifying the resource type. It distinguishes itself from siblings like deploy_vm_from_template and vm_clone.

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 specifies when to use this tool (for local .ova files) and when not (for vSphere templates, cloning existing VMs), naming alternative tools directly.

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