sdcloud_get_device_interface_subinterfaces

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

No annotations are provided, so the description carries the full burden. It only states 'list', implying a read operation, but does not disclose pagination behavior, rate limits, or whether the operation is idempotent. The name 'get' hints at read-only, but the description lacks explicit safety guarantees.

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 with no fluff. Every word is necessary and front-loaded. It achieves maximum conciseness.

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 list operation with pagination parameters and no output schema, the description is minimal. It covers the core purpose but does not mention that the tool returns a list, how pagination works, or the meaning of the filter parameter. Given the simple nature, it is barely adequate.

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 input schema covers 60% of parameters with descriptions (from, size, filter). The description adds no extra meaning beyond the schema. For the two required parameters (device_uuid, interface_name) without schema descriptions, the description does not clarify them. Baseline 3 is appropriate due to partial schema coverage.

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 'List' and a precise resource 'subinterfaces configured under a specific interface on a device'. This clearly defines the tool's scope and distinguishes it from the sibling tool `sdcloud_get_device_config_subinterfaces`, which lists subinterfaces at a config level.

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 no guidance on when to use this tool vs alternatives. For example, it does not mention that this tool is more specific than `sdcloud_get_device_config_subinterfaces` or when pagination parameters should be used.

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