esxi_list_snapshots

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. The phrase 'List all' implies a read-only, unfiltered operation, but it does not disclose the return structure, any pagination behavior, or error handling, all of which are relevant for a list operation.

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 sentence packed into the essential function: 'List all snapshots of a VM on ESXi'. It is perfectly front-loaded and contains zero unnecessary words.

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?

The tool is simple, with only two well-documented parameters. However, since there is no output schema, the description does not specify what snapshot information is returned (e.g., names, IDs, timestamps), nor any potential error conditions, leaving some gaps in completeness.

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 input schema has 100% description coverage for its two parameters (vm_id and device_id), both clearly labeled as 'VM identifier' and 'ESXi host device ID'. The tool description adds minimal extra meaning beyond confirming the relationship between VM and host, so a baseline score of 3 is appropriate.

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 verb 'list' and the resource 'snapshots of a VM', explicitly naming the domain (ESXi). It distinguishes itself from sibling tools like esxi_create_snapshot, esxi_delete_snapshot, and esxi_revert_snapshot by being the read-only listing operation.

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 usage is implied: the tool should be used when one needs to enumerate all snapshots of a specific VM. However, it does not explicitly mention alternatives or exclusions, such as when to use create/delete/revert snapshot tools instead.

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