list_snapshots

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

Annotations already declare readOnlyHint=true and destructiveHint=false, which establishes the safety profile. The description adds meaningful context about the synthetic 'current' entry and the confirm token included for each snapshot, enriching expectations of the output. No contradictions with annotations.

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 one sentence of about 24 words, front-loaded with the core action and resource. Every phrase adds value: the synthetic 'current' entry and the confirm token purpose. No redundancy or filler.

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's simple parameter set, the presence of an output schema, and annotations covering safety, the description is complete. It adds the key context about the token and synthetic entry that structured data does not provide. No critical information is missing for an agent to use it correctly.

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% for the single required parameter vmid. The description implies vmid is the identifier of the VM or container by saying 'of a VM or container', providing minimal compensation. It does not explain format or how to obtain the value, but for a simple integer parameter this is adequate.

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?

Description states the verb 'List' and the resource 'snapshots of a VM or container', which is specific and clear. It also mentions the synthetic 'current' entry and the confirm token, making it distinct from other list-type sibling tools like list_backups or list_guests.

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 usage context by noting the confirm token is needed for delete or rollback, signaling when this tool is a prerequisite. However, it does not explicitly name alternatives or give when-not-to-use guidance, so it falls short of a 5.

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