slide_list_device_vlans

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

No annotations are provided, so the description must carry the behavioral transparency burden. It only says 'List' and does not disclose whether results are paginated, sorted, limited, or whether any authorization constraints apply. It also does not clarify whether 'configured VLAN interfaces' includes only active VLANs or all defined ones.

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, compact sentence that immediately conveys the tool's core function. There is no redundant wording or irrelevant detail, making it easy for an agent to parse quickly.

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 tool is simple with one parameter, so the description is mostly adequate for invoking it correctly. However, it lacks guidance on how this differs from slide_get_device_vlan, does not mention pagination or return value shape, and provides no behavioral context such as read-only status. Given no annotations or output schema, more context would be valuable.

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 100%, with device_id described as 'Device ID.' The description does not add additional meaning to the parameter, but the schema already fully documents it, so the 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 clearly states the action ('List') and the resource ('a device's configured VLAN interfaces'). It is distinct from sibling tools like slide_get_device_vlan, which retrieves a single VLAN rather than listing all configured VLAN interfaces for a device.

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 when to use the tool: when you need the configured VLAN interfaces for a specific device. However, it does not explicitly state alternatives, such as using slide_get_device_vlan for a single VLAN, nor does it mention any exclusions or prerequisites beyond needing a device_id.

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