vm_list

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

With no annotations provided, the description carries the full disclosure burden, yet it never states that this is a read-only, side-effect-free operation. It also omits whether results are paginated, how many guests are returned, or what a "future registered" guest means in practice.

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 front-loaded sentence with no filler; the resource and its scope appear immediately. Nothing in the sentence is redundant.

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 simple zero-argument listing tool this is close to adequate, but with no output schema and no annotations the agent has no idea what the returned guest records contain or how to consume them. One clause about the return shape would close the gap.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate beyond the schema. The baseline for a parameterless tool applies, with no compensating detail needed.

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?

States a specific verb ("Discover") and resource ("registered VMware guests and their configured capabilities"), so an agent knows this enumerates VMs. The phrasing "current and future registered" is slightly ambiguous (pending vs. already-registered guests), and it never explicitly distinguishes itself from siblings, though none of the listed siblings are enumeration tools.

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?

No when-to-use guidance is given, no prerequisites, and no mention of related tools such as vm_status or vm_connect for follow-up actions. Usage is only implied by the verb "Discover".

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