startall_node

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

With no annotations, the description bears full burden. It discloses the core behavior (start VMs and containers) and parameter effects (force, vms list). However, it does not mention prerequisites (e.g., node availability) or detailed side effects beyond starting.

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: two sentences plus a brief args list. The main purpose is stated first, and every sentence adds value without redundancy.

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?

The description covers input parameters and basic behavior. Since an output schema exists, return values need not be detailed. However, it lacks context such as error conditions (e.g., node offline) or confirmation of boot order handling, making it slightly incomplete for a bulk operation.

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 0%, so the description must compensate. It provides a clear 'Args' section explaining each parameter: node (node name), force (force start if running), vms (comma-separated VMIDs, empty for all). This adds critical meaning beyond the schema types and defaults.

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 'Start all VMs and containers on a node (respecting boot order).' It uses a specific verb ('Start') and resource ('all VMs and containers on a node'), clearly distinguishing it from siblings like start_container, start_vm, and stopall_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 implies usage context by mentioning boot order and the ability to filter VMs or force start. However, it does not explicitly state when not to use this tool or compare to alternatives like bulk_start_guests, leaving some implicit guidance.

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