Stop recovery mode

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

Annotations already indicate a mutating, destructive, and idempotent operation. The description adds meaningful behavioral context by warning that the operation fails if the VM is not currently in recovery mode, and by explaining the resulting state change back to normal operation. This is valuable beyond the annotations, though it does not detail any other side effects.

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 concise and well-structured: a direct first sentence states the action, a second sentence flags the failure condition, and a third sentence provides the purpose and expected outcome. No filler or redundant 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 simple one-parameter tool without an output schema, the description is complete: it states the action, the precondition, and the intended result. Nothing essential is missing for an agent to decide when and how to call this endpoint.

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% and the single parameter `virtualMachineId` is documented as "Virtual Machine ID." The description only references "a specified virtual machine" without adding further semantic detail, so the schema carries the full weight for parameters. A baseline score of 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 a specific verb and resource: "Stop recovery mode for a specified virtual machine." It further clarifies the outcome by noting the operation "exit[s] system rescue mode and return[s] VPS to normal operation," which distinguishes it clearly from related VPS lifecycle operations.

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 states when to use the tool: "Use this endpoint to exit system rescue mode and return VPS to normal operation." It also gives a key precondition: calling it on a VM not in recovery mode will fail. It does not explicitly name an alternative such as VPS_startRecoveryModeV1, but the usage context is clear enough.

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