list_vms

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

With no annotations, the description carries the full burden. It discloses that the tool returns specific VM attributes, supports OData filtering, and auto-paginates when limit is omitted. It does not mention authentication or performance implications, but is informative enough for safe usage.

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?

Three efficient sentences: purpose, returned data, filtering capability. No fluff, each sentence earns its place. Well-structured for quick reading.

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 list tool with no output schema, the description adequately lists return fields. It covers both parameters' behaviors (filter, limit) and mentions auto-pagination. While it could detail output format more, it is sufficient for an agent to invoke correctly.

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 100%, baseline 3. The description adds value by explaining the 'limit' parameter's default behavior ('Omit to retrieve all') and giving OData filter examples, enhancing the schema's 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 the tool's action ('List virtual machines on Nutanix') and specifies return fields (VM names, UUIDs, power states, resource allocation). It distinguishes itself from sibling tools like create_vm or get_vm by focusing on listing multiple VMs with optional filtering.

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 description mentions OData filtering support with examples, but does not explicitly state when to use this tool versus alternatives like get_vm for a single VM or pe_list_vms for a different endpoint. However, it provides clear context on OData usage and limit behavior.

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