reinstall_vps

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

The description goes well beyond the annotations by explicitly warning that the operation is irreversible, that everything on the disk is lost, that the VPS must be stopped, and that confirm=true is required. It also discloses OS availability constraints per VPS, giving the agent critical operational context beyond the structured annotations.

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 compact and front-loaded with the most important fact: the operation wipes the disk and is irreversible. Every sentence adds meaningful guidance, and there is no filler or repetition of schema 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?

For a destructive operation with no output schema and no parameter descriptions, this is close to complete: it covers prerequisites, the confirm flag, OS sourcing, and the destructive outcome. The only meaningful gap is the undocumented new_pass parameter, which prevents it from being fully 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 description coverage, the description carries the full burden for parameter semantics. It usefully explains os_id and confirm, but it does not describe new_pass at all, leaving its meaning, format, and constraints to inference. vps_id is self-evident, but the missing new_pass guidance prevents a higher score.

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 identifies the verb and resource: it wipes the VPS's boot disk and reinstalls a fresh OS. It also communicates the irreversible nature of the operation, making it easy to distinguish from related operations like change_vps_hostname or create_vps.

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 strong usage context: the VPS must already be stopped, stop_vps is named as the prerequisite step, confirm=true is required, and os_id must come from list_vps_available_os. It does not explicitly state when not to use this tool versus alternatives, so it falls just short of a 5.

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