VPS_recreateVirtualMachineV1

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

The description explicitly states irreversibility, data loss, deletion of snapshots, password checking against leaked databases, and password requirements. No annotations provided, so description carries full burden and does so thoroughly.

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 clear sections (main description, password requirements, warning). It is comprehensive but slightly verbose; could be tightened while retaining all critical information.

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?

No output schema exists. The description explains the effect, side effects, and prerequisites well. However, it does not explicitly describe the response format or what happens after operation (e.g., async action details).

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 100% with descriptions. The description adds value by detailing password requirements (leaked check, length, character classes) and notes that panel_password is ignored if unsupported, beyond what the schema provides.

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 recreates a virtual machine from scratch, reinstalling the OS and resetting to initial state. It distinguishes from siblings like VPS_restartVirtualMachineV1 or VPS_restoreSnapshotV1 by specifying it's a destructive rebuild.

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 says 'Use this endpoint to completely rebuild VPS instances with fresh OS installation.' It provides clear context for when to use, but does not explicitly mention alternatives or when not to use.

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