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

The description adds substantial behavior beyond the annotations: the hosted box sleeps after inactivity, wakes on the next call, services recover sequentially over a couple of minutes, and sleeping stops scheduled jobs, bots, queue workers and webhook receivers. It also warns that a not-yet-ready service is not broken and should be retried.

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 front-loaded with the core purpose and then moves into operational caveats. It is longer than a minimal description, but the wake/sleep behavior is material and most sentences earn their place.

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, open-world tool with no output schema and a nested arguments object, the description provides the behavioral context an agent needs: what it may change, how to use next_step tools, and how to handle sleeping/waking delays.

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 100%, so node_id, tool_name and arguments are already fully documented in the schema. The description does not add parameter-specific semantics beyond what the schema provides, which is acceptable given the complete coverage.

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 ('Call') and resource ('one machine MCP tool... on one selected Nerdit node') and gives examples of mutation types (deploy, stop, write files, set secrets). It also distinguishes itself from the read-tool sibling by explaining that read-only machine tools are accepted only to support next_step calls.

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?

It explains the intended context clearly: call a write-capable machine tool on a selected node, and optionally use it for read-only next_step tools. However, it does not explicitly say when to prefer the sibling nerdit_call_read_tool, leaving a small routing ambiguity.

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