nodes_restart_all

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

No annotations are provided, so the description carries full burden. 'Restart all nodes' implies a potentially disruptive operation affecting multiple system components, but it doesn't disclose critical behavioral traits like required permissions, whether this is reversible, expected downtime, confirmation prompts, or rate limits. This is inadequate for a tool with clear operational impact.

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 perfectly concise at three words ('Restart all nodes') with zero wasted language. It's front-loaded with the essential 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 potentially disruptive bulk operation tool with no annotations and no output schema, the description is insufficiently complete. It doesn't address what 'restart' entails, what happens to services during restart, whether there's confirmation, what the return value indicates, or error conditions. The context demands more operational clarity.

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 tool has zero parameters with 100% schema description coverage, so the schema fully documents the lack of inputs. The description doesn't need to add parameter information, and it correctly implies no parameters are required for this bulk operation. Baseline 4 is appropriate for zero-parameter tools.

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 'Restart all nodes' clearly states the action (restart) and target (all nodes), which is a specific verb+resource combination. However, it doesn't explicitly differentiate from its sibling 'nodes_restart' (which likely restarts individual nodes), leaving some ambiguity about when to use each.

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. With sibling tools like 'nodes_restart' (likely for individual nodes), 'nodes_disable', 'nodes_enable', and 'nodes_reset_traffic', there's no indication of when a bulk restart is appropriate versus other node management operations.

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