snapshot_create

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

No annotations are provided, so the description carries full burden. It discloses the write nature, risk level, undo recording mechanism, and dry_run behavior. Missing details like permissions or failure behavior, but sufficient for a snapshot tool.

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 structured with a title line and a parameter list, using concise language. Every sentence adds value, no redundancy. Perfectly sized.

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 no output schema, the description explains the snapshot creation process, undo recording, and dry_run. It doesn't describe return values, but for a create tool this is acceptable. Missing some edge case details, but overall 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?

With 0% schema coverage, the description thoroughly explains all four parameters: vm_id (with reference to vm_list), name (with example), dry_run (effect), and target (default behavior). This adds significant value 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 explicitly states 'Snapshot a VM' with a clear verb and resource, and mentions the inverse operation (delete snapshot), which helps distinguish it from sibling tools like snapshot_list or snapshot_revert.

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 provides context for usage (creating a snapshot, dry_run preview) and mentions the inverse operation, but lacks explicit guidance on when not to use it or direct comparison with siblings. However, it is still clear enough for an agent.

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