VPS_createSnapshotV1

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

The description discloses a critical behavioral trait: 'Creating new snapshot will overwrite the existing snapshot!' This is essential for understanding the tool's impact. With no annotations provided, the description carries the full burden of behavioral transparency, and it adequately warns about the destructive overwrite behavior.

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 with two paragraphs and a bold warning. It is relatively concise, though the third sentence in the first paragraph ('A snapshot captures...') could be shortened slightly. Overall, it is effectively sized and front-loaded.

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 the tool has only one parameter, no output schema, and no annotations, the description provides adequate context: purpose, behavioral warning, and usage guidance. It does not explain return values or error conditions, but for a simple creation tool, this is sufficient.

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 100% description coverage for the single parameter 'virtualMachineId' (described as 'Virtual Machine ID'). The tool description does not add additional meaning beyond what the schema provides, so the baseline score of 3 is appropriate.

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's verb and resource: 'Create a snapshot of a specified virtual machine.' It distinguishes from sibling tools like VPS_deleteSnapshotV1, VPS_restoreSnapshotV1, and VPS_getSnapshotV1 by focusing on the creation action.

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 states when to use the tool: 'Use this endpoint to capture VPS state for backup and recovery purposes.' It does not provide explicit when-not-to-use scenarios or list alternative tools, but the context implies alternatives like restore or delete snapshots.

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