reinstall_vps

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

Annotations already declare destructiveHint=true, and the description adds valuable context by specifying the destructive behavior: it wipes and reinstalls, which tells the agent what gets destroyed. This goes beyond the bare annotation without being redundant.

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?

A single, punchy sentence front-loaded with 'DESTRUCTIVE' that immediately communicates the tool's nature and function. Every word earns its place; no waste.

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 tool with no output schema, the description covers the core action and destructive nature. It does not mention the confirm parameter's purpose or potential downtime, but the schema provides the parameter details and the destructive hint is already highlighted. Overall, it is sufficiently complete for an agent to use the tool safely.

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 description coverage is 100%, with all three parameters (service_id, os, confirm) already described. The description adds no additional parameter-specific meaning beyond the phrase 'given OS image,' which maps to the 'os' parameter. Baseline 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 uses specific verbs 'wipe and reinstall' and identifies the resource ('the VPS') and the key input ('a given OS image'). It clearly distinguishes this from sibling tools like power_vps, set_hostname, and cancel_service, leaving no ambiguity about the operation.

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 implies usage (when you need to reinstall with a new OS), but it does not explicitly state when to prefer this over alternatives or mention any prerequisites or exclusions. There is no explicit context like 'use when the current OS is corrupted' or 'do not use if you need to preserve data.'

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