pve_node_start_all

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

With no annotations provided, the description carries full burden but only states the basic action. It doesn't disclose critical behavioral aspects: whether this requires administrative privileges, what happens if some VMs/containers fail to start, if there's a startup order, timeout behavior, or any side effects on node resources. The 'force' parameter hints at potential issues but isn't explained.

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 a single, clear sentence with zero wasted words. It's front-loaded with the core action and scope, making it immediately understandable without unnecessary elaboration.

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 tool that performs a potentially impactful bulk operation on virtual infrastructure with 3 parameters and no annotations or output schema, the description is insufficient. It doesn't address safety considerations, error handling, performance implications, or what constitutes successful completion. The context demands more guidance for responsible use.

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 100%, so parameters are well-documented in the schema itself. The description adds no additional parameter semantics beyond implying bulk operation through 'all VMs and containers.' It doesn't explain the relationship between 'node' parameter and the scope, or clarify when to use the optional 'vms' parameter versus the default 'all' behavior.

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 the action ('Start') and target resources ('all VMs and containers on node'), providing a specific verb+resource combination. However, it doesn't explicitly differentiate from sibling tools like 'pve_start_vm' or 'pve_start_container' that start individual resources, though the 'all' keyword implies a bulk operation.

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 like starting individual VMs/containers or using other node management tools. It lacks context about prerequisites, dependencies, or typical scenarios for bulk starting.

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