proxmox_node_bulk

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

With no annotations, the description carries full burden. It only hints at elevated permissions but does not disclose whether the operations are synchronous, destructive, or how failures are handled. The behavioral impact of bulk operations is largely underspecified.

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 extremely concise with only two sentences, front-loading the purpose and actions. Every word adds value, and there is no redundancy or unnecessary detail.

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 the complexity of bulk operations (5 parameters, no output schema, no annotations), the description is incomplete. It lacks information about return values, error handling, concurrency implications, and the exact scope of 'all' guests. Users need more context to use this tool safely.

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 schema already covers 80% of parameters with descriptions. The description repeats the action enum values, adding marginal value. It does not elaborate on the meaning or interaction of parameters like 'target' or 'with-local-disks' beyond what the schema provides.

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 performs bulk guest operations with specific actions (start_all, stop_all, migrate_all). It distinguishes from sibling tools like proxmox_guest_start/stop/migrate which operate on individual guests, though it could be more explicit that it applies to all guests on the node.

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 no guidance on when to use this tool versus alternatives. It does not mention prerequisites, such as elevated permissions implied by 'all elevated', or scenarios where single operations are preferred. Missing context for effective tool selection.

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