Stop Recovery Mode

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

With no annotations, the description carries the full burden. It discloses an important behavioral trait—that the VM will reboot normally after exiting recovery mode—but it does not mention potential downtime, prerequisites, or whether recovery mode must be active. The reboot detail adds value, but the description is otherwise sparse.

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, focused sentence: 'Exit recovery mode and reboot normally.' It is concise, front-loaded, and every word contributes meaning. No redundant or irrelevant information is included.

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 simple tool with one required parameter and no output schema, the description sufficiently conveys the action and the significant side effect (reboot). Minor details like whether the VM must already be in recovery mode could be added, but overall it is adequately complete for invocation.

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 fully describes vm_id (type: number, description 'Virtual machine ID'), and the tool description adds no additional parameter context. Since schema coverage is 100%, the baseline of 3 applies; the description does not enhance parameter understanding.

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 'Exit recovery mode and reboot normally' clearly states a specific action: terminating recovery mode and initiating a standard reboot. It distinguishes itself from sibling tools like vps_recovery_start (which enters recovery mode) and vps_restart (which reboots without exiting recovery mode).

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 the tool should be used when the user wants to leave recovery mode and reboot the VM normally, but it does not explicitly state when to use it versus alternatives, nor does it mention any prerequisites or exclusions. This is implied usage rather than clear guidance.

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