list_vm_snapshots

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

No annotations are provided, placing the full burden on the description. The description only states the listing behavior and fields returned, but does not disclose whether it is read-only, any authorization needs, or performance implications. The behavioral transparency is minimal.

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 a single sentence of 10 words, which is concise but at the expense of necessary details. It is appropriately front-loaded but lacks explanations for parameters and usage context.

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 that there is an output schema (not shown), the return values might be documented elsewhere. However, the description does not cover parameter semantics, pagination, or ordering. For a listing tool with two undocumented parameters, the description is incomplete.

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?

The input schema has two parameters (cluster, namespace) with no default descriptions (0% coverage). The description does not explain what these parameters do or how they affect the results. The agent receives no additional meaning beyond the 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 lists VirtualMachineSnapshots and mentions specific fields (phase, source VM, ready status). It distinguishes from siblings like list_volume_snapshots by naming a different resource type. However, it does not mention that the list can be filtered by cluster/namespace, which might be relevant for differentiation.

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?

No guidance is provided on when to use this tool versus alternatives like list_volume_snapshots or get_virtual_machine. There is no mention of prerequisites, context, or scenarios where this tool is preferred.

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