vm_power_on

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

With no annotations, the description discloses it's a write operation with medium risk, handles ETags, and is reversible. It could mention behavior when VM is already on, but overall good 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 clear and front-loaded with the purpose. The arg list is structured, though it could be slightly more concise by omitting redundant formatting. Still, it is effective.

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 tool with 3 parameters and no output schema, the description adequately covers setup, arg meanings, risk, and reversibility. It is sufficiently complete for an agent to use correctly.

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 0%, but the description explains each parameter: vm_ext_id from vm_list, dry_run for preview, target for config. This fully compensates for the lack of schema descriptions.

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 'Power on a VM' with a note on reversibility, and the name is explicit. It distinguishes from sibling tools like vm_power_off and vm_reboot.

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 provides arg details but does not explicitly state when to use this tool vs alternatives like vm_power_off. The note 'reversible → power-off' implies context, but no explicit guidance is given.

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