stop_node

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

No annotations are provided, so the description must cover behavioral traits. It describes the stop action but does not disclose impacts such as whether stopping disrupts connections, requires specific permissions, or is reversible. This leaves significant gaps in understanding the tool's effect.

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 concise with two sentences and a parameter list. Every sentence adds value. Minor improvement: the parameter list could be presented more compactly.

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 context of 2 parameters, no annotations, and low schema description coverage, the description is adequate but not complete. An output schema exists but is not used—the description does not explain the return value. More details on behavior and constraints would improve 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%, so the description must add meaning beyond the schema. It explains that node_id can be omitted to stop all nodes, but it does not clarify the format of node_id (integer or null) beyond what the schema already says. The description partly compensates for low coverage but not fully.

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 the tool stops one node or all nodes if `node_id` is omitted. The verb 'stop' and resource 'node' are specific, and the behavior is distinct from siblings like 'start_node' and 'wipe_node'.

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 explains the basic usage (omitting node_id stops all nodes) and mentions the required lab_path parameter. However, it does not explicitly state when to use this tool over alternatives like 'wipe_node', nor does it give conditions where stopping should be avoided.

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