proxmox_node_action

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

No annotations are provided, so the description must fully disclose behavior. It mentions actions (reboot/shutdown) which imply mutations, but gives no details on destructive nature, prerequisites, or side effects. Essential behavioral traits are missing.

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 short, which is concise, but it is under-specified. The two sentences do earn their place, but more structure (e.g., separating purpose from parameters) would improve 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 no annotations and an output schema that is not described, the description leaves many gaps: no return value explanation, no prerequisites, and no warnings about destructive actions. It is incomplete for a tool performing node-level operations.

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 description adds the allowed values for 'action' (reboot, shutdown), compensating for the schema's lack of enums and zero coverage. However, it does not explain the 'node' parameter or provide additional context 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 clearly identifies the resource as 'Proxmox node' and lists specific actions (reboot, shutdown), distinguishing it from sibling tools for containers and VMs. However, the verb 'Run an action' is generic.

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 is provided on when to use this tool versus alternatives, or when to choose reboot vs shutdown. The description implicitly suggests node-level use via the name, but lacks explicit usage context.

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