nodes_restart_node

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It says nothing about the impact of a restart (disconnects active connections, downtime, forceRestart semantics), whether it requires confirmation, or that it is a destructive operation. For a restart action with zero annotation coverage, this is a serious gap.

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's short, but that brevity reflects under-specification rather than effective conciseness. The leading line is just a route/tag dump rather than a useful front-loaded summary of the action and its constraints.

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?

A mutation action tool with 3 parameters (including a nested required boolean), no annotations, no output schema, and no guidance on effect or confirmation. The definition is insufficient for an agent to call it correctly and safely.

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 only 33%. The schema documents `confirm` but leaves `uuid` and the required nested `body.forceRestart` undocumented in prose; the description adds no meaning for any parameter. It does not compensate for the coverage gap.

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 the HTTP method, path, and resource ('Restart node'), which tells the agent this restarts a specific node. However, it's essentially a restatement of the route plus a two-word phrase, with no differentiation from siblings like nodes_restart_all_nodes or nodes_bulk_nodes_actions. It's minimally clear but not more.

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 about when to use this tool versus nodes_restart_all_nodes, nodes_bulk_nodes_actions, or node lifecycle tools like nodes_disable_node / nodes_enable_node. The description offers no usage context at all.

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