list_vm_snapshots

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered. The description adds genuine beyond-annotation context: the return envelope shape, level semantics, empty-items meaning, and the teaching-error behavior on unknown names.

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?

Front-loaded with the [READ] marker and purpose, then return semantics, then routing guidance. A couple of phrases (the truncated-False explanation) are slightly verbose but each sentence carries useful information.

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?

For a read-only list tool with no output schema, the description supplies return structure, level semantics, empty-result meaning, error behavior, and alternative-tool routing. Only minor gaps remain, such as pagination/truncation mechanics beyond the empty-items note.

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 100%, so both parameters (target, vm_name) are already documented in the schema. The description notes vm_name must come from list_virtual_machines and that an unknown name yields a teaching error, which is mild added meaning over the schema baseline.

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?

Specific verb+resource ('List all snapshots of one VM') with explicit scope ('including the nesting hierarchy'). It distinguishes itself from siblings by naming find_aging_snapshots as the sweep alternative and confining itself to one known VM.

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?

Clearly states when to use this (one known VM) versus find_aging_snapshots (whole-inventory sweep), and routes the agent to list_virtual_machines for the name. Lacks explicit when-not conditions beyond the sibling contrast, but the context is clear.

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