vsphere_list_vms

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

Annotations already mark it as read-only and idempotent; the description adds behavioral details like result capping, the truncated field, and glob matching semantics for name filters, which go beyond the structured 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?

The description is compact, front-loaded with a one-line summary, and the Args list is structured and free of fluff. Every sentence 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?

Given 11 optional parameters and an output schema, the description covers filter semantics, pagination, and the truncated flag, making it sufficient for correct invocation. The output schema presumably covers return values, so no need to describe them.

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?

With 0% schema description coverage, the description's Args section fully documents all 11 parameters, including types, semantics, and examples (e.g., substring matching, glob support, power_state values). This adequately compensates for the lack of schema descriptions.

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 'List virtual machines with power state, resources and guest details' – a specific verb and resource that distinguishes it from sibling tools like get_vm or list_hosts.

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?

It explains that filters are combined with AND and provides pagination instructions with the truncated field and offset, giving clear context for how to use filters and page. It does not explicitly name alternatives, but the listing vs getting distinction is evident from the description.

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