add_to_ipv6_address_list

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

With no annotations, the description carries the full burden and does so well: it declares this is a WRITE tool gated behind MIKROTIK_ALLOW_WRITE=true, describes the dry-run/apply confirm pattern and its default, and discloses two specific error behaviors (duplicate list_name+address pair, disabled ipv6 package) with the guarantee that no duplicate is ever created.

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-loaded with the core purpose, then structured with IMPORTANT/behavioral blocks that are easy to scan. It is on the longer side and the guard/duplicate/error notes are dense, but nearly every sentence adds decision-relevant information rather than restating the schema.

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 guarded 6-parameter mutation tool with no annotations, it covers purpose, safety gating, dry-run semantics, error conditions, and the key conceptual caveat about firewall rules. An output schema exists, so return-value explanation is correctly omitted, leaving nothing an agent needs in order to call this correctly.

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. It explains `address` (IPv6 only, IPv4 rejected before touching the device), `list_name` (the referenced list), and `confirm` (False=preview, True=apply), but leaves `comment`, `timeout`, and `device_name` unexplained. The critical and non-obvious parameters are covered, so it substantially closes the 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+resource: adds an IPv6 address/subnet to a named IPv6 firewall address-list at `/ipv6/firewall/address-list`. It explicitly distinguishes itself from the IPv4 sibling (`add_to_address_list`) and by extension from `remove_from_ipv6_address_list`, so an agent can route correctly without opening any 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?

Gives explicit when-not guidance: 'this only manages the *list* - it does NOT create or modify any firewall rule,' and notes traffic is only affected if an existing filter rule references `list_name`. It also spells out the two-step confirm workflow (preview with confirm=False, apply with confirm=True) and names the IPv4 counterpart it mirrors.

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