VPS_startRecoveryModeV1

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

The description discloses key behaviors (boot from recovery disk, mount original disk at /mnt) but omits side effects like VM restart/downtime, that recovery mode must be stopped explicitly, or any response format. With no annotations, the burden is higher.

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 well-structured: main action first, then explanation, then details, then usage directive. It is concise without unnecessary words, though could be slightly tighter.

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 lacks crucial context: no output schema meaning the agent doesn't know what the response is (e.g., action ID, success status), no mention of async nature or how to monitor progress, and no prerequisites such as VM being stopped. Incomplete for a potentially long-running operation.

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 coverage is 100% with adequate parameter descriptions. The tool description does not add extra semantic value beyond what the schema already provides, so baseline 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 clearly states the tool initiates recovery mode for a VM, explains what recovery mode is for, and distinguishes it from other VPS management tools like VPS_stopRecoveryModeV1. The action is specific and well-contextualized.

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,' providing a use case but lacking explicit when-not-to-use guidance or alternatives. It does not mention prerequisites like VM state or potential conflicts with other operations.

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