Start recovery mode

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

The description discloses concrete behavioral effects: 'Virtual machine will boot recovery disk image and original disk image will be mounted in /mnt directory.' This adds value beyond the annotations (readOnlyHint=false, destructiveHint=false) by explaining what actually happens to the VM. It does not contradict the 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 front-loaded with the core purpose and then provides necessary context about recovery mode and the mount behavior. It is somewhat verbose with the use-case enumeration (repairing file systems, recovering data, troubleshooting), but each sentence contributes useful context and the length is appropriate for an operation of this significance.

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 covers the main effect (booting recovery disk, mounting /mnt) and the endpoint's purpose. However, it does not mention important operational details such as whether the VM will be rebooted/stopped, potential downtime, how to exit recovery mode (sibling tool exists), or what the response will look like. Given the absence of an output schema, these gaps leave the agent with some uncertainty about the full impact of the call.

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%: both 'virtualMachineId' and 'root_password' are documented in the input schema. The description adds minimal parameter-specific meaning beyond the schema, only clarifying that recovery mode is a special state. This meets the baseline of 3 for full schema coverage.

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's purpose: 'Initiate recovery mode for a specified virtual machine.' It explains the resource (virtual machine) and the action (start recovery mode), and elaborates on the use cases. However, it does not explicitly differentiate from the sibling tool VPS_stopRecoveryModeV1, though the verb 'start' versus 'stop' is implicit.

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 enable system rescue operations on VPS instances,' providing general guidance on when to use it. It does not mention alternatives or exclusions, such as when the VM should be stopped or when recovery mode should not be used, leaving the usage context implied rather than explicit.

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