Retrieve all configured subinterfaces for a device. Use this to inspect interface details or verify device network configuration.
List all of a device's configured subinterfaces.
| Name | Required | Description | Default |
|---|---|---|---|
| from | No | Starting index for pagination (zero-based). Default 0. | |
| size | No | Max results per page. 0 returns the API-imposed maximum. | |
| filter | No | Filter condition to apply to the results. | |
| device_uuid | Yes |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided, so description must disclose behavioral traits. It does not mention pagination (from/size parameters), filtering capability, or that it is a read-only operation. The description is too brief to inform accurate invocation.
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, but it omits essential behavioral and usage context. Being concise is not helpful if it sacrifices completeness needed for correct tool invocation.
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?
Given the tool has 4 parameters, no output schema, and no annotations, the description is insufficient. It does not explain pagination, filtering, or the response format. Siblings with similar names are not distinguished, leading to potential confusion.
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 description coverage is 75% (3 of 4 parameters have descriptions). The description adds no parameter-specific information beyond what is in the schema. Baseline 3 is appropriate as the schema already documents most parameters adequately.
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?
Description states verb 'List', resource 'subinterfaces', and scope 'of a device'. It is clear and specific. However, it does not differentiate from the sibling 'sdcloud_get_device_interface_subinterfaces', which may list subinterfaces of a specific interface, but still distinguishes itself by implying 'all' subinterfaces.
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 on when to use this tool versus alternatives like 'sdcloud_get_device_interface_subinterfaces'. The description does not provide context for selection or mention prerequisites for using the tool.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.