remove_from_ipv6_address_list

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

No annotations are present, so the description carries the full behavioral burden and does so well: it declares this is a WRITE tool, that it is blocked unless MIKROTIK_ALLOW_WRITE=true, the two-step preview/confirm safety pattern, IPv6-only validation that rejects IPv4 before touching the device, and two explicit error conditions (no matching entry, ipv6 package disabled).

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?

Multi-paragraph but front-loaded: the action and match key come first, followed by validation, then the write-guard and confirm workflow. Every block carries information, though the formatting is slightly heavier than strictly needed.

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 values need not be described, and the description covers everything else an agent needs: mutation semantics, the environment gate, the confirm two-step, IPv6 validation, and the failure modes. Nothing essential for correct invocation is missing.

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 coverage is 0%, so the description must compensate, and it does: it defines `address` as required-IPv6, ties `list_name`+`address` together as the match key, and explains `confirm`'s default-false preview semantics. Only `device_name` is left implicit, which is minor given its obvious meaning.

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+resource ('Remove the entry ... from an IPv6 firewall address-list') with the exact API path, and names its sibling ('Mirrors `remove_from_address_list` on the IPv6 menu'), letting an agent distinguish the IPv6 variant from the IPv4 one without opening either schema.

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?

Explains the operative workflow clearly: call with confirm=False for a preview, then confirm=True to actually remove, plus the MIKROTIK_ALLOW_WRITE gate. It does not explicitly enumerate when to prefer this over add_to_ipv6_address_list or the IPv4 tool, but the IPv6 framing and sibling reference make the context clear.

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