vm_power_on

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

Annotations already mark it as idempotent and non-destructive. The description adds '[WRITE]' indicating mutation. However, it does not disclose preconditions (e.g., VM must exist and be in powered-off state) or error conditions.

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, only three lines, with the action prefix '[WRITE]' front-loaded. 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?

For a simple power-on operation, the description covers inputs and basic action. It misses preconditions but an output schema exists (not shown) to cover return values. Could improve by noting required 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?

With 0% schema coverage, the description fully explains both parameters: 'Exact name' for vm_name and 'Optional target' with default fallback, adding significant value beyond the schema.

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 tool name 'vm_power_on' and description '[WRITE] Power on a virtual machine' clearly state the action and resource. It is easily distinguished from sibling 'vm_power_off'.

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 indicates when to use (to power on a VM) but does not explicitly mention prerequisites like VM must be powered off or when not to use. Still, the purpose is clear given the name.

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