Start all VMs/CTs on node

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

Annotations indicate non-readonly and non-destructive, but description adds no behavioral details (e.g., behavior if VMs are already running, prerequisites, error handling). Without annotations, the description carries full burden, but it fails to disclose these traits.

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?

Single sentence is concise but lacks necessary detail. Not overly verbose, but could be more informative without loss of brevity.

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 3 parameters and no output schema, the description is insufficient. It omits explanation of parameter behavior (e.g., vms filtering, force usage) and return value. Relies heavily on schema which itself is incomplete.

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 low (33%): only 'vms' has a description. The tool description says 'all', but the 'vms' parameter allows filtering, creating ambiguity. No clarification of 'force' or 'node' semantics beyond 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?

Description clearly states 'Bulk-start all VMs and containers on a node', specifying the verb (start), resource (all VMs/CTs), and scope (node). It distinguishes from siblings like start_vm, start_container, and node_stop_all.

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 such as start_vm, start_container, or node_migrate_all. The description implies a bulk operation but lacks explicit context for selection.

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