node_remove

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

The description adds valuable behavioral context beyond the annotations: it warns that removal should follow draining and leaving the swarm, and that force is required for active/reachable nodes. This expands on the destructiveHint=true annotation without contradicting it, giving the agent a clearer picture of consequences and prerequisites.

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 efficiently structured: a one-line summary, a brief usage paragraph, and an args/returns list. Every sentence provides necessary information without redundancy or padding, making it easy to scan and understand.

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 swarm operation with two parameters, the description covers all essential aspects: purpose, prerequisites, force behavior, parameter descriptions, and the return type. Even though an output schema exists, the description supplements it with the return value explanation. This is complete for an agent to select and invoke the tool correctly.

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?

With schema description coverage at 0%, the description fully compensates by documenting each parameter: `id_or_name` is clearly defined as the node id or name to remove, and `force` is explained as forcing removal of an active/reachable node. This adds semantic meaning beyond the bare schema types and defaults.

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 opens with 'Remove a node from the swarm,' using a specific verb and resource. It clearly distinguishes this from sibling tools like node_update (which updates node properties) and node_list (which lists nodes), leaving no ambiguity about its function.

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 provides clear usage context: a node should normally be drained via `node_update` with Availability 'drain' and have left the swarm first, and active/reachable nodes require `force=True`. This effectively states when to use the tool and the prerequisites, though it could more explicitly differentiate from alternatives beyond the node_update reference.

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