Manage firewall address lists

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=false and openWorldHint=true, so the safety profile is covered. The description adds nothing behavioral: it does not say whether adding an existing entry duplicates or errors (notably with idempotentHint=false), how removal behaves when the entry is absent, or that timeout creates auto-expiring entries.

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 with zero filler. It is efficient, though its brevity comes at the cost of the missing detail flagged in other dimensions.

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 7-parameter mutating tool with no output schema and under half of parameters documented, one sentence is not enough. An agent gets no information on list creation, duplicate handling, removal semantics, or what the response contains.

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 only 43% across 7 parameters. The description mentions no parameters at all, leaving 'list', 'action' (the enum), 'comment', and 'ipv6' undocumented in both places, so it fails to compensate for the coverage gap.

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 pair (add/remove) and resource (firewall address list), plus the typical intent (block/allow hosts). It is clearly narrower than the generic siblings mikrotik_add/mikrotik_remove, but the description never names those siblings to make the distinction explicit.

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 parenthetical 'commonly used to block or allow hosts' explains intent, not tool selection. There is no guidance on when to use this versus mikrotik_add, mikrotik_remove, or mikrotik_firewall_add_rule, and no stated prerequisites (e.g. whether the list must already exist).

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