pve_shutdown_vm

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

There are no annotations, so the description must carry the load. It says 'gracefully' and mandates confirm, but does not disclose timeout behavior, force_stop semantics, or potential side effects of a shutdown. This is minimal for a state-changing 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?

Two short sentences with no filler; the core action is front-loaded and every word contributes meaning. The terseness is almost too sparing, but as a concise summary it works.

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 6-parameter mutation tool with zero schema descriptions and no annotations, this description is severely incomplete. It does not explain vm_type choices, force_stop/timeout roles, or the safety significance of confirm beyond a passing mention. The existence of an output schema slightly reduces return-value burden, but operational guidance is still far too thin.

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 description coverage is 0%, and the description only addresses confirm. It leaves node, vmid, timeout, vm_type, and force_stop unexplained, forcing an agent to guess their meanings from schema structure alone.

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 states a clear action ('gracefully shut down') and resource ('VM/container'), which distinguishes it from pve_stop_vm (force stop) and pve_reboot_vm. The word 'gracefully' signals the operational intent unambiguously.

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?

It provides one explicit requirement ('Requires confirm=true'), but does not name alternatives or describe when to choose graceful shutdown over stop/reboot. The usage context is implied rather than explicit.

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