Start Recovery Mode

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 revealing side effects such as VPS downtime, loss of normal network access, or the need to explicitly stop recovery mode afterward. This is minimal disclosure for a state-changing operation.

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 5-word sentence with no filler, front-loading the action and target. It is appropriately concise for a one-parameter 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?

The description is extremely minimal and lacks important context for an agent: what recovery mode entails, when it should be used (e.g., for troubleshooting), whether the VPS must be stopped first, and how to return to normal mode. It also does not reference related tools like vps_recovery_stop, leaving the agent to infer the full workflow.

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 one required parameter, vm_id, with a description 'Virtual machine ID' (100% schema coverage). The tool description adds no additional meaning beyond the schema, so the baseline score of 3 applies.

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 action ('Boot') and resource ('VPS') with a specific target ('recovery mode'), which distinguishes it from normal start (vps_start) and recovery stop (vps_recovery_stop). It is concise and unambiguous, though it does not explicitly mention the VM ID parameter or the recovery mode's purpose.

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?

No guidance is given on when to use recovery mode versus normal operations, nor does it mention prerequisites, alternatives, or how to exit recovery mode. The tool is listed among many VPS lifecycle tools, but the description provides no context for selection.

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