vm_snapshots

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

With no annotations, the description carries the full behavioral burden. "List" weakly implies a read-only operation, but it does not state whether snapshots are per-VM, ordering, freshness, or whether an empty result is possible; there is no real disclosure of behavior.

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 words, front-loaded with the verb, with no filler whatsoever. It is efficient, though the extreme terseness leaves room that could have been used for behavioral context.

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 zero-parameter list tool with no output schema, the description never indicates what a snapshot record contains or how results are shaped. It is minimally adequate to select the tool but incomplete for interpreting results.

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 and the schema is empty, so there is nothing for the description to clarify. Baseline 4 applies for a no-argument tool.

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?

"List saved snapshots" pairs a specific verb with a specific resource, so the agent knows this enumerates existing VM snapshots. It does not explicitly name the related siblings (vm_save, vm_status), but the resource distinction is strong enough to separate it from those.

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?

There is no guidance on when to call this versus vm_status or vm_save, no preconditions, and no stated exclusions. The agent must infer from the name alone that this is the discovery step before restoring or starting from a snapshot.

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