address_lists

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

No annotations are provided, so the description carries full behavioral burden. It does disclose the returned fields and the read-before-write relationship with the add/remove tools, which is useful readable context. But it is silent on whether this is read-only (implied by 'list'), pagination, performance on large lists, or device_name targeting/auth requirements.

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?

Front-loads the purpose and resource path, then the returned fields, then the related tools. Well-structured and mostly tight. The quoted example ('blocked-clients') costs a few words but is justified as illustrative context.

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?

An output schema exists, so return-value shape need not be explained in detail, and the description still helpfully names the fields. It correctly situates the tool in the read/write workflow with its add/remove siblings. The gap is that the single required parameter (device_name) is undocumented given 0% coverage.

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?

One required parameter (device_name) with 0% schema description coverage. The description never explains what device_name means or that the tool operates against a specific router. For a required parameter with zero schema documentation, the description should compensate but does not.

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) and resource (firewall address-list entries), names the concrete RouterOS path /ip/firewall/address-list, and enumerates the fields returned (list, address, timeout, dynamic, disabled). This distinguishes it from plausible siblings like ipv6_firewall_address_lists and firewall_filter.

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?

Provides a clear use case — 'See who's currently in which named list... before adding/removing entries' — and routes the agent to the mutation siblings add_to_address_list / remove_from_address_list. It gives the pre-read context explicitly. No explicit when-not-to-use is stated, which keeps it below 5.

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