list_snapshots_vm

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

With no annotations provided, the description carries the full burden for behavioral disclosure. It only restates the purpose without mentioning permissions, error handling, output format, or side effects. For a list operation, it could at least note that it is read-only or returns snapshot metadata, but it doesn't.

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, front-loaded sentence with no unnecessary words. It immediately identifies the action and object, making it highly scannable and efficient.

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 the tool has no annotations and no output schema, the description must provide richer context. It fails to explain the 'node' parameter, address edge cases like no snapshots, or indicate what the response looks like. The description is too minimal for reliable agent use.

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 description coverage is 0%, so the description must compensate for the unexplained parameters. It hints that vmid identifies the virtual machine, but 'node' is entirely unaddressed, leaving a required parameter ambiguous and increasing the risk of incorrect invocation.

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 action 'List' and the object 'all snapshots for a specified virtual machine'. It distinguishes from sibling tools like list_snapshots_container by explicitly targeting VMs, and from snapshot creation/deletion tools by its read-only 'List' verb.

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 implies the tool is for retrieving VM snapshots, but it does not explicitly state when to use this over alternatives like list_snapshots_container, nor does it mention pr prerequisites or exclusions. The context is clear but the guidance is only implicit.

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