Restart virtual machine

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

Annotations already convey that the operation is mutating (readOnlyHint=false) and non-destructive (destructiveHint=false). The description adds a useful edge case: 'If the virtual machine was stopped, it will be started.' It does not explain timing, service interruption, or error behavior, but the main behavioral nuance is disclosed.

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?

Three sentences, but the last one ('Use this endpoint to reboot VPS instances.') is largely redundant with the first sentence and the tool name. The first two sentences are informative and front-loaded; trimming the final sentence would improve structure.

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 single-parameter restart endpoint with annotations covering mutation and non-destruction, the description covers the core action and the stopped-VM behavior. It omits asynchronous behavior and error details, but given the low complexity and no output schema, this is minimally sufficient.

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 has 100% coverage with virtualMachineId described as 'Virtual Machine ID.' The description refers only to 'specified virtual machine' and adds no extra meaning about how to obtain or format the ID. The baseline score of 3 applies because the schema already documents the single parameter fully.

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?

States a specific verb and resource ('Restart a specified virtual machine') and defines the operation as 'fully stopping and starting' it. This distinguishes it from sibling tools VPS_startVirtualMachineV1 and VPS_stopVirtualMachineV1 by making it explicit that a restart is a full stop/start cycle.

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?

Offers no decision guidance about when to use this tool versus the sibling start/stop tools. The sentence 'Use this endpoint to reboot VPS instances' restates the purpose rather than describing conditions, prerequisites, or alternatives. An agent gets no help choosing between restart, start, or stop.

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