list_wireless_access_list

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

Annotations already declare readOnlyHint=true and idempotentHint=true. The description adds a vague warning that behavior differs across RouterOS versions; this is some behavioral context, but it does not explain how it differs, what to expect, or any side effects. It does not contradict the annotations, but its contribution is minimal.

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 extremely short, but it is under-specified rather than concise. It uses its one sentence to issue a vague warning instead of conveying useful purpose or usage details, so it fails to earn its place.

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?

Even though an output schema exists, the description neither explains the tool's function nor mentions what it lists. Given the low complexity (1 optional parameter), the description could easily have clarified the resource being accessed, but it remains completely inadequate for an agent to understand the tool's role.

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 sole parameter 'device' is entirely undocumented in both the schema and the description. With 0% schema description coverage, the description provides no semantic meaning beyond the parameter's name, leaving the agent without guidance on accepted values or format.

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 does not state what the tool does. It only warns that it is a 'Legacy function' and 'different in RouterOS v7.x', leaving the agent to infer the purpose from the name alone. It does not distinguish this tool from its siblings, such as list_wireless_security_profiles or get_wireless_registration_table.

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?

There is no guidance on when to use this tool or when to prefer alternatives. The 'Legacy function' label might imply less preferred, but it stops short of suggesting an alternative or specifying appropriate contexts, making the description unhelpful for tool selection.

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