hostodo_power_vm

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

With no annotations, the description must fully disclose behavior, but it only lists actions. It fails to mention whether actions are immediate, if confirmation is required, what the impact is on running processes, or error conditions. The description is too terse to inform the agent of behavioral traits.

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 minimal and efficiently communicates the core action. However, it could benefit from a structured format (e.g., bullet points) or example values for clarity.

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 two parameters, no output schema, and no annotations, the description is insufficiently complete. It lacks information about return values, error handling, and the effects of each action on the VM 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; the description merely repeats the enum values for 'action' without explaining what each does. The 'vm_id' parameter is not described at all, leaving the agent without context on how to obtain or format it.

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 identifies the tool's purpose: power-control a VPS. It lists all valid actions (start, shutdown, reboot, stop, reset), which distinguishes it from other VPS management tools that perform different operations (e.g., reinstall, execute commands).

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 on when to use this tool versus alternatives. It does not specify prerequisites, state requirements, or distinguish between similar actions. For example, it does not explain the difference between 'stop' and 'shutdown' or 'reboot' and 'reset'.

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