Start VPS

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

With no annotations provided, the description must carry the full burden of behavioral disclosure. It only states the action, omitting any side effects (e.g., VM must be powered off, boot time, billing implications) or what happens after execution. The agent cannot anticipate outcomes or failure modes.

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, front-loaded sentence that directly states the purpose. It is not verbose, though it could benefit from a bit more context; however, the brevity is appropriate for a simple one-parameter action.

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 action with one parameter, the description plus schema provides the minimum needed to invoke the tool. However, it lacks context about VM state (e.g., must be stopped first) or what the expected result is, leaving some ambiguity for the agent.

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 schema fully documents vm_id with a description and 100% coverage, so the description does not need to add parameter details. It adds no extra meaning beyond the schema, which aligns with the baseline of 3.

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 'Start' and identifies the resource as 'a virtual machine', which clearly differentiates it from sibling actions like vps_stop, vps_restart, and vps_docker_start. The scope is unambiguous and matches the tool name and title.

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?

No guidance is provided on when to use this tool versus alternatives such as vps_restart or vps_recovery_start. There are no exclusions, prerequisites, or references to other tools, leaving usage context entirely up to the agent.

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