list_base_vm_snapshots

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

Annotations mark this as a safe read-only operation, and the description adds critical behavioral context beyond that: snapshots taken before Horizon Agent installation will cause AGENT_CUSTOMIZATION_FAULT / IC Agent missing, so names should be checked for agent-related indicators. This is exactly the kind of failure-mode transparency an agent cannot infer from 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?

Front-loads the tool's purpose, then the downstream usage, then a focused caution. Every sentence earns its place by preventing a known provisioning failure or clarifying snapshot selection.

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?

An output schema exists, so return-value details are appropriately left out of the description. The description covers the remaining agent needs: what the tool lists, how the output connects to create_desktop_pool/create_rdsh_farm, and the snapshot-selection pitfall.

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 description coverage is 100%, so both vcenter_id and base_vm_id are already documented in the schema. The description adds useful downstream meaning for the returned id, but it does not further explain the input parameters beyond what the schema already provides.

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?

Starts with a specific verb and resource: 'List snapshots of a base VM.' It immediately explains the snapshots' purpose as images for instant clone pools or farms, which clearly distinguishes it from sibling tools such as list_base_vms and list_vm_templates.

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?

Explicitly states when and how to use the result: the returned id becomes base_snapshot_id in create_desktop_pool or create_rdsh_farm when source is INSTANT_CLONE. It also warns against naive selection and says to ask the user when in doubt, covering when-not and alternative decision paths.

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