nodes_restart_all

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

Annotations already declare readOnlyHint=false and destructiveHint=true, so the description is not responsible for the basic safety profile. It adds useful blast-radius context with "EVERY node", but does not explain forceRestart behavior, downtime impact, reversibility, or permissions.

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 a single front-loaded imperative phrase with no wasted words. It is arguably too terse for a destructive all-node operation, but the sentence itself is structurally efficient.

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 destructive operation that restarts every node, the description is missing parameter semantics, prerequisites, warnings, and alternatives. Annotations provide the destructive hint, but the text does not complete the picture an agent needs before invoking it.

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 only parameter, forceRestart, has 0% schema description coverage and is never mentioned in the description. The description adds no meaning about what forceRestart changes or when to set it true versus false.

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), resource (node), and scope (EVERY), making clear this is an all-node restart rather than the single-node nodes_restart sibling. An agent can identify the action and blast radius immediately from the text.

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 gives no when-to-use guidance, no prerequisites, and no comparison to alternatives such as nodes_restart or nodes_bulk_actions. The word EVERY implies scope but does not say when this tool should be chosen over siblings.

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