nodes_restart_all_nodes

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

With no annotations, the description carries the full behavioral burden and largely fails: it does not state that restarting all nodes is disruptive/downtime-inducing, what permissions are required, or what happens to active connections. The 'POST /api/nodes/actions/restart-all' line only weakly signals that this is a mutating operation.

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?

It is short and front-loaded, but the raw route string and 'Tags: Nodes Controller' line are noise that consume space without adding decision-relevant information. No sentence here earns much beyond restating the name.

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 fleet-wide mutating operation with no annotations, no output schema, and an undocumented required parameter, the description omits critical context: impact/downtime, auth requirements, and the meaning of forceRestart. It is too thin for a destructive-scoped action.

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 50%: the required forceRestart boolean is undocumented in both schema and description, and the description says nothing about either parameter. Only the confirm parameter has schema-level explanation, so the description does not compensate for the gap on the required field.

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?

"Restart all nodes" states a verb and resource with the scope 'all', so the meaning is graspable, but it is essentially the tool name de-underscored and adds no differentiation from siblings like nodes_restart_node or nodes_bulk_nodes_actions. The route line adds only the HTTP method/path, not conceptual clarity.

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?

There is no guidance on when to use this versus nodes_restart_node (single node) or nodes_bulk_nodes_actions, nor any prerequisite or exclusion noted. The only extra text, 'Tags: Nodes Controller', is organizational metadata rather than usage direction.

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