remove_node

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

With no annotations provided, the description carries the full burden. It does disclose a key behavioral trait: the node and its attached links/interfaces are removed. However, it does not mention whether the action is irreversible, requires stopping the lab, or any other side effects.

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 sentence with a clear verb-first structure. It is concise and front-loaded with the action, containing no unnecessary information.

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?

The description covers the core purpose but lacks details about safety, irreversibility, or preconditions. Since the tool is destructive and has no annotations, more context would be expected. The presence of an output schema reduces the need to explain return values, but the behavioral and usage context remains incomplete.

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 schema has 0% description coverage and the description does not explain 'lab_id' or 'node_id' beyond the general context of 'lab' and 'node'. It does not state which parameter identifies which resource, so the description adds little meaning over the schema's names.

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 uses a specific verb ('Remove') and identifies the resource ('node') and scope ('any links/interfaces attached to it'). It clearly distinguishes this tool from the sibling 'remove_link' by noting the cascading removal of attached links and interfaces.

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 implies when to use the tool (when removing a node from a lab) but does not explicitly state exclusions or reference alternatives like 'remove_link' for link-only removal. The context of the siblings suggests that 'remove_link' is for links only, but this is not spelled out.

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