snapshot_aging

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

Annotations already indicate readOnlyHint=true, destructiveHint=false. The description adds that est_size_mb is a lower-bound due to API limitations, mentions the return structure, and reinforces read-only behavior. This provides context beyond 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 well-structured: starts with a [READ] header, a concise one-sentence summary, a clarifying contrast, return format details, and a parameter list. Every sentence is informative 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?

Despite no output schema, the description explains the exact return structure (total_snapshots, old_snapshots, vms_with_snapshots, etc.) and details about est_size_mb. Given the tool's complexity (sweep all VMs, return structured data), this is complete.

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%, so description carries the full burden. It lists all four parameters with defaults and meanings: age_threshold_days, only_old, target, limit. This adds significant value beyond the input schema.

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 the tool sweeps all VMs for snapshots and flags old/sprawling ones, contrasting with vm_list_snapshots which covers only one VM. This provides a specific verb (sweep, flag) and resource (all VMs snapshots), distinguishing it from siblings.

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 explicitly contrasts with vm_list_snapshots and notes that snapshot deletion should be done via another tool (vmware-aiops). This tells the agent when to use this tool and when not to, including alternatives.

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