Retrieves fabric-wide control connection links between devices filtered by state (up or down) to inspect control plane connectivity.
Fabric-wide: list control connection links between all devices in the given state.
| Name | Required | Description | Default |
|---|---|---|---|
| state | Yes | Link state |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full behavioral burden. 'List' implies a read-only operation, but it does not explicitly state side-effect profile, permissions, return shape, or pagination behavior.
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?
A single front-loaded sentence with no wasted wording. The scope qualifier is placed first, making the tool's breadth immediately clear.
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 one-parameter read-only list tool, the description is sufficient to invoke it correctly, but without an output schema or annotations it leaves return shape and pagination unspecified. Adequate but with clear gaps.
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 single parameter is an enum with a description. The description adds no parameter details beyond the schema's 'state' enum, which is the expected baseline when the schema already documents the input.
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?
States a specific verb ('list'), resource ('control connection links'), and scope ('Fabric-wide ... between all devices') plus a state filter. Clear enough to distinguish from a device-specific control connection query, though it does not explicitly name siblings like get_control_connections.
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 use for fabric-wide control-link queries in a given state, but provides no explicit when-to-use guidance, prerequisites, or alternatives such as get_control_connections or get_control_connections_history.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.