proxmox_node_power

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

The description notes that all actions are 'elevated', indicating required privileges, but does not elaborate on whether shutdown is graceful/forced, reboot behavior, or wakeonlan prerequisites. No annotations exist to supplement.

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 and to the point, but could be better structured (e.g., bullet list) without losing brevity. No waste, but slightly too terse.

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 power control tool with no output schema, the description lacks details on how actions are performed (ACPI, WoL), error conditions, or return values. Minimal completeness given the tool's critical nature.

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 50% (node has description, action does not). The description only repeats the enum values without explaining each action's effect, and adds no detail on the node parameter 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 description explicitly states 'Node power control' and lists the three actions (shutdown, reboot, wakeonlan), clearly identifying the tool's purpose and distinguishing it from guest power control siblings.

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 does not explicitly state when to use this tool versus alternatives like proxmox_guest_shutdown, but the domain is implied by 'Node' and the sibling tools provide context. Lacks explicit when/when-not guidance.

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