node_reload

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

The description discloses that the tool restarts a node but provides no additional behavioral traits such as side effects, required node state, or permissions. With no annotations, this is insufficient.

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 very concise (4 words) but lacks structure and does not add value beyond restating the name. It could be improved with context.

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?

Given the tool has 2 parameters with no schema descriptions, the description does not provide enough context. The output schema exists but is not referenced. The tool is a mutation without annotations, requiring more completeness.

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%, and the tool description does not explain the parameters 'node_id' or 'project_id'. This leaves the agent without guidance on how to fill the inputs.

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 clearly states 'Reload (restart) a node,' providing a specific verb and resource. It distinguishes from the sibling tool 'nodes_reload_all' by implying a single node, though not explicitly stated.

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?

No usage guidelines are provided. There is no context about when to use this tool versus alternatives like node_start, node_stop, or nodes_reload_all.

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