VPS_stopRecoveryModeV1

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

With no annotations provided, the description carries the full burden. It discloses that the operation fails if the VM is not in recovery mode, but does not elaborate on other behavioral traits such as auth requirements, whether it is asynchronous, or if other side effects occur.

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 consists of three concise sentences, each adding value: the action, a precondition, and the purpose. No extraneous 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?

Given the tool has one parameter and no output schema, the description sufficiently covers the context: it explains when it works, when it fails, and what it achieves. It could mention potential asynchronous behavior or expected response, but is not incomplete.

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 already describes the parameter 'virtualMachineId' as 'Virtual Machine ID' with 100% coverage. The description adds no additional semantic value beyond referencing 'specified virtual machine', which is redundant.

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 'stop recovery mode' for a specified VM, and distinguishes it from sibling tools like VPS_startRecoveryModeV1. It also explains the failure condition and the outcome of returning to normal 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 explicitly indicates when to use: to exit system rescue mode and return to normal. It also states that the operation fails if the VM is not in recovery mode, implying it should only be used when appropriate. However, it does not mention alternatives or when not to use.

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