list_vm_snapshots

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

While annotations correctly mark the tool as readOnlyHint=true and destructiveHint=false, the description adds no additional behavioral context, such as output format, pagination behavior, or permission requirements. Reliance on annotations alone is acceptable but the description misses an opportunity to enrich transparency.

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 with no redundant or irrelevant information. It is concise and front-loaded, delivering the core purpose efficiently.

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 lacks an output schema, and the description does not describe the return value (e.g., list of snapshot IDs, names, timestamps). Given the complexity of a list operation, this omission leaves the agent without important context about what to expect from the tool.

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?

Input schema coverage is 100% with descriptions for both parameters (node and vmid). The description does not add extra meaning beyond the schema, which is acceptable given high coverage, but it does not clarify expected formats or constraints.

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 'List all snapshots of a VM' clearly states the verb (list), resource (snapshots of a VM), and scope (all). It is specific and distinguishes this tool from sibling tools like create_vm_snapshot, delete_vm_snapshot, and list_container_snapshots.

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 provides no guidance on when to use this tool versus alternatives. Sibling tools such as create_vm_snapshot or list_container_snapshots are not mentioned, nor is there any indication of prerequisites or context for usage.

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