list_base_vms

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds the meaningful filter that only instant-clone-eligible VMs are returned, but says nothing about pagination, empty results, or result richness beyond what the output schema carries.

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?

A single tight sentence that front-loads the action and the qualifying scope with zero filler. Every clause earns its place.

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?

For a read-only list tool with a complete schema, an output schema, and annotations covering safety, the description is sufficient to invoke it correctly. It would be fully complete with a brief note on when to prefer it over the vm_templates or base_vm_snapshots siblings.

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 both vcenter_id and datacenter_id are fully documented in the schema, with the vcenter_id description even pointing to list_virtual_centers. The description adds no parameter-level meaning beyond that, so the baseline 3 applies.

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?

Specific verb (List) plus resource (VMs in vCenter) plus a clear scope qualifier (usable as base images for instant clone pools/farms). This distinguishes it from nearby siblings like list_vm_templates and list_base_vm_snapshots, though it never names them explicitly.

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 'base images for instant clone pools/farms' phrasing implies when the tool is relevant, and the schema notes list_virtual_centers for obtaining IDs. However there is no explicit when-to-use/when-not, nor any routing to the template/snapshot siblings an agent might confuse it with.

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