vpc_reboot_instance

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

No annotations exist, so the description must fully disclose behavioral traits. The description simply states 'Reboot a VSI' with no details about whether the reboot is graceful or forceful, whether it requires the instance to be running, what happens to state, or whether it is synchronous. This is severely lacking for a potentially destructive operation.

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 very concise (one sentence), but at the cost of missing critical information. It is not overly verbose, so it scores average. However, it could be expanded slightly to include key behavioral or parameter details without losing conciseness.

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?

Given the tool has 2 parameters, no output schema, and no annotations, the description is far from complete. It does not mention whether the operation returns a status, requires specific permissions, or has any side effects. A reboot tool should at least indicate if it is a soft or hard reboot and any prerequisites on the instance state.

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 0% description coverage and the description adds no parameter information. The two parameters (instance_id, region) are not explained at all, leaving the agent to infer their meaning from the parameter names alone. No enums or constraints are provided.

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 'Reboot a VSI' clearly states the action (reboot) and the resource (VSI, which stands for Virtual Server Instance). It distinguishes from sibling tools like vpc_start_instance and vpc_stop_instance, as reboot is a distinct operation. However, the acronym VSI may not be universally understood by all agents, slightly reducing clarity.

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 usage guidelines are provided. The description does not indicate when to use this tool versus alternatives such as vpc_start_instance or vpc_stop_instance. There is no explicit context or prerequisites mentioned, leaving the agent without guidance on appropriate invocation scenarios.

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