proxmox_guest_reboot

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

No annotations are provided, so the description bears full responsibility for behavioral disclosure. It states 'reboot' (a restart) and mentions elevation, but does not describe side effects (e.g., VM unavailability during reboot, graceful vs. forceful) 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?

A single sentence that immediately conveys the core action and resource types. No redundant words. Front-loaded with the verb 'Reboot', making it efficient for an AI agent to parse.

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?

Lacks information about return values or behavior after the reboot command. No output schema is provided, so the agent has no indication of what to expect (e.g., success acknowledgment, error messages). Incomplete for a tool with no output schema.

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 explains the 'type' parameter (VM vs. LXC), which compensates for its missing schema description. Node and vmid are already described in the schema, so the description adds value for the enum parameter. Overall, it enhances understanding beyond the structured input.

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 it reboots a VM or LXC container, specifying the resource types. It is distinct from sibling tools like shutdown or stop, though not explicitly contrasted. The verb+resource combination is specific and unambiguous.

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 on when to use this tool versus alternatives like shutdown or stop. Only mentions that elevated permissions are required, which is a prerequisite but not a usage cue. Lacks context on appropriate scenarios.

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