bridge_vlans

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

With no annotations, the description carries the behavioral burden and does a good job: it discloses that `current-tagged`/`current-untagged` are conditionally present, version-dependent, and never invented. It does not discuss authentication, rate limits, or pagination, but for a read-only list tool with an output schema this is a minor gap. No contradiction with structured fields.

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 front-loaded with the table and fields, then explains the sibling distinction and caveats. It is somewhat verbose with parentheticals and line breaks, but most sentences carry useful information and nothing is egregiously redundant.

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 tool with an output schema, the description is complete: it identifies the exact table, return columns, version-dependent fields, and the key sibling distinction for managed-switch VLAN filtering. An agent has enough context to select and invoke the tool correctly.

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?

There is one required parameter (`device_name`) and schema description coverage is 0%, so the description is expected to compensate. Instead, it never explains what `device_name` means, what values are accepted, or where to obtain it. The parameter is conventional, but the definition itself provides no additional semantic guidance.

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 resource ('bridge VLAN filtering table entries') and gives the RouterOS path `/interface/bridge/vlan`. It explicitly distinguishes this tool from the similarly named `list_vlans`/`add_vlan`/`remove_vlan` siblings, which operate on a different RouterOS mechanism.

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?

It clearly states when to use this tool ('a switch that segments traffic by VLAN across bridge ports needs THIS table, not `/interface/vlan`') and names the alternatives that should not be used for this purpose. It also routes the agent to `bridge_ports` for related per-port configuration.

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