tdarr_disconnect_node

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

The word 'Forcefully' implies a potentially destructive action, but no further details are given about effects, authorization needs, or rate limits. With no annotations, the description should disclose more about the operation's impact.

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 extremely concise with no wasted words. For a simple tool with one parameter, this length is appropriate and front-loaded.

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 does not explain return values, possible errors, or side effects. For a potentially destructive action, more context is needed despite the tool's simplicity.

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 covers the single parameter 'nodeID' with a description. The tool description adds no extra meaning beyond the schema, so baseline score of 3 is appropriate.

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 'Forcefully disconnect a node' uses a specific verb and resource, clearly indicating the action and target. It distinguishes the tool from siblings like 'tdarr_restart_node' or 'tdarr_update_node', though it could be more explicit about the context.

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 guidance is provided on when to use this tool versus alternatives, such as 'tdarr_update_node' or 'tdarr_restart_node'. There is no mention of prerequisites, when not to use it, or expected outcomes.

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