pve_list_snapshots

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

Annotations provide readOnlyHint=true. Description adds that PVE includes a synthetic 'current' entry, parent links form a tree, and returns a JSON list with specific fields. No contradiction. Helpfully details return format and source endpoint.

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?

Four sentences: purpose, applicability, return format, source. Every sentence adds value. No fluff. Well-structured.

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?

With output schema present, description covers parameters and return fields. Given simplicity, no gaps.

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 coverage is 0%. Description explains vmid locates the VM, node is optional and auto-resolved, adding meaning beyond the schema. No further details on formats, but sufficient.

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 'List snapshots of one VM or container.' It uses a specific verb (list) and resource (snapshots of one VM/container), and distinguishes from sibling tools like pve_snapshot_create, pve_snapshot_delete, etc.

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?

Description states it applies to a single VM/CT located by vmid, with node optional and auto-resolved. It mentions the synthetic 'current' entry and parent links, providing context. No explicit when-not-to-use or alternatives, but it's clear.

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