device_list

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

With no annotations present, the description carries the full burden, and it does disclose two meaningful traits: no device connection occurs and no credentials are exposed. That is solid safety context for an inventory call, though it says nothing about whether results are cached or how connectivity-independent discovery works.

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?

A single front-loaded sentence whose second clause earns its place by stating the safety guarantee. No filler, no restatement of the tool name.

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-format details are rightly omitted, and a zero-parameter list tool needs little else. The description is nearly complete; adding which sibling to use instead would close the gap.

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 tool takes zero parameters and the schema is empty with 100% coverage, so there is no parameter semantics to convey. Baseline of 4 applies.

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 (configured RouterOS devices), making the operation unambiguous. It also implicitly separates itself from the command_execute sibling by clarifying that this path does not connect to devices. It stops short of naming the sibling outright, which is the only thing keeping it from a 5.

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?

Usage is implied: the 'without connecting to them or exposing credentials' clause suggests this is the safe inventory path versus actually running commands. There is no explicit when-to-use/when-not statement or named alternative, so an agent must infer that command_execute is the contrasting tool.

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