vm_list

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

Annotations already establish read-only, idempotent, and non-destructive behavior, so the safety profile is clear. The description adds one useful behavioral detail, that results are scoped by an "optional allowlist," but it does not explain what that allowlist is or how visibility is determined beyond that.

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 a single short sentence with no wasted words, and the core purpose is front-loaded. Its brevity does not create structural issues for such a simple no-argument tool.

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?

With no parameters, full annotation coverage, and an output schema, the description only needs to identify the listing operation and scope. It does that adequately, though the undefined "optional allowlist" leaves a small ambiguity about what determines visibility.

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?

There are zero parameters, so parameter semantics are not a burden on the description. The mention of an "optional allowlist" is not a schema parameter and is slightly ambiguous, but it does not affect invocation correctness.

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 states a specific verb and resource: "List VMs." It also adds scope with "visible through the optional allowlist," but it does not explicitly distinguish this from siblings such as vm_get or vm_wait.

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 gives no explicit guidance on when to use this tool versus alternatives like vm_get for details or vm_wait for state changes. The listing purpose is implied, but there is no when/when-not guidance.

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