nodes_restart

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

Annotations declare this is a write operation (readOnlyHint=false) that is not destructive (destructiveHint=false), which the description does not contradict. But the description adds nothing beyond the annotations: it doesn't disclose that restarting a node disconnects active users, what forceRestart does differently, or any permission requirements.

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?

At two words the text is not bloated, but it is under-specified rather than concise. There is no front-loaded detail to structure, and the fragment carries none of the context needed to invoke the tool correctly.

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 required-parameter mutation tool with 0% schema coverage and no output schema, the description is far too thin. An agent gets no information on parameter semantics, side effects, or how this differs from nodes_restart_all.

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 0%, so both required parameters (uuid, forceRestart) are undocumented in the structured data. The description compensates only marginally by implying the tool targets a single node, leaving the uuid format and the meaning of forceRestart entirely unexplained.

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 states a specific verb ('Restart') and resource ('node'), so an agent knows exactly what operation is performed. However, it offers no differentiation from the sibling nodes_restart_all, which is the obvious alternative for the same action at a different scope.

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 tool versus nodes_restart_all, nodes_disable, or nodes_update. No prerequisites, no mention that the node must be reachable, and no context about the forceRestart flag's effect on the operation.

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