Create VPS Snapshot

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only states the action without mentioning whether snapshot creation is asynchronous, requires a running VM, incurs costs, or affects existing snapshots. This lack of side-effect and requirement info is a significant gap.

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, efficient sentence with no unnecessary words. It is front-loaded and appropriately sized for a simple tool.

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 basic create operation with one parameter, the description is minimal but lacks context about the operation's effects, timing, or requirements. Without annotations or an output schema, an agent would need more behavioral details to use the tool safely and correctly.

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 schema fully documents the only parameter (vm_id) with its description and 100% coverage, so the tool description adds no additional meaning beyond the schema. Baseline 3 is appropriate since the schema does the heavy lifting.

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 states a clear verb ('Create') and resource ('snapshot of a virtual machine'), which distinguishes it from sibling snapshot operations like vps_get_snapshot, vps_restore_snapshot, and vps_delete_snapshot. However, it relies on the tool name for VPS context and doesn't explicitly mention scope, so it's clear but not deeply differentiated.

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 no guidance on when to use snapshots vs backups, prerequisites (e.g., VM must exist or be running), or alternatives. It doesn't mention exclusions or contrast with related tools like vps_get_backups or vps_restore_backup.

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