Batch Restart VPS

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

The description adds no behavioral detail beyond what the destructiveHint annotation already conveys. It does not mention potential downtime, irreversibility, or any effects on the VPS instances beyond 'restart'. Since annotations already flag destructive behavior, the description contributes little extra transparency.

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 short sentence with no wasted words. It effectively communicates the core function without redundancy or filler.

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 tool is simple with a single parameter and no output schema, but the description omits usage guidance and any behavioral caveats. It is adequate for a straightforward operation, but leaves the agent to rely on the sibling list and annotations for context. Missing explicit when-to-use guidance (e.g., vs vps_restart) prevents a higher score.

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 fully describes the vm_ids parameter with a clear description ('Array of virtual machine IDs to restart'). The tool description does not add any additional parameter semantics, so the schema carries the explanatory burden. Baseline score of 3 is appropriate given 100% schema coverage.

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 verb 'restart' and the resource 'VPS instances', and specifies the batch nature ('multiple ... at once'), which distinguishes it from the single VPS restart sibling tool (vps_restart). It is specific and unambiguous.

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 implies use for restarting multiple VPS instances at once, but it does not explicitly state when to prefer this over vps_restart or mention any alternatives. The context is inferable from the word 'batch' and 'multiple', but there is no explicit guidance or exclusion.

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