VPS_restartVirtualMachineV1

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

Discloses that the tool performs a full stop and start, and handles the case where the VM is already stopped. With no annotations, this is reasonable disclosure, though additional safety notes are absent.

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 concise sentences, each adding value: definition, edge case handling, and usage directive. No wasted words.

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?

Lacks mention of return values or expected response (e.g., action ID). For a simple restart, this is a gap but not critical given the tool's nature.

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%, and the description adds no extra meaning beyond the schema's 'Virtual Machine ID'. Baseline 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?

Description uses specific verb 'Restart' and resource 'virtual machine', clearly indicating a full stop and start. It distinguishes from sibling start/stop tools by implying a reboot, but does not explicitly name alternatives.

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?

Explicitly states 'Use this endpoint to reboot VPS instances', providing clear usage context. However, lacks guidance on when not to use it or mention of alternative sequences like stop then start.

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