snapshot_list

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

The description explicitly marks the tool as [READ] and details the return format including the truncated flag, indicating non-destructive behavior. It does not cover auth or rate limits, but these are not required for a simple read 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 concise and well-structured with a summary, return format, and argument list. Every sentence adds value without redundancy.

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 3 optional parameters and no output schema, the description provides the return format, filter behavior, and default values. It covers the essential information for an agent to use the tool 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 coverage is 0%, but the description explains each parameter: vm_id as optional UUID filter, limit as max snapshots with default 200, target as Xen Orchestra target name. This adds meaning beyond the schema's types and defaults.

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 it lists VM snapshots with optional filtering by VM, using the verb 'List' and resource 'VM snapshots'. It distinguishes from sibling snapshot tools (create, delete, revert) and provides return format.

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 indicates the tool is for listing snapshots with optional filtering. It does not explicitly state when to use this vs alternatives like vm_list or backup_job_list, but the context is clear. No exclusionary guidance.

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