disconnect_cables

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

The annotations already establish that this is not read-only, and the description adds useful scope by clarifying that instance_id causes ALL attached cables to be disconnected, which is a materially destructive bulk operation. However, it does not mention irreversibility, required device state, permissions, or partial-failure behavior for a mutation tool.

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?

One front-loaded sentence with no filler. Both modes are stated compactly and every phrase contributes to understanding the operation.

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 core action is clear, but with zero required parameters the description should clarify what happens if both cable_ids and instance_id are omitted or provided together. For a destructive mutation with no output schema and minimal annotations, this leaves an important behavioral gap.

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 coverage is 100%, and the schema itself describes both cable_ids and instance_id. The description restates their purpose but adds no extra semantics such as precedence when both are provided or behavior when neither is supplied, so it meets the baseline rather than exceeding it.

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 and resource ('Disconnect cables') and clearly covers both operating modes: by cable_id or by device instance_id. It is easy to distinguish from connect_cables, though it does not explicitly name that sibling.

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 lays out the two usage modes directly: pass specific cable_ids to disconnect individually, or pass an instance_id to remove all attached cables. It gives clear context for selecting an input but does not state exclusions, prerequisites, or whether both parameters may be combined.

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