list_ipv6_addresses

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

The annotations already declare readOnlyHint=true and idempotentHint=true, so the description does not need to restate safety. It adds some context by explaining the meaning of global and link-local addresses, but does not describe return format, pagination, or other behavioral traits beyond what annotations provide.

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 a single purpose sentence followed by three concise bullet notes. It is front-loaded, free of filler, and every line adds useful information. The structure is easy to scan.

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?

With 7 optional parameters and an output schema present, the description covers some filtering specifics but leaves several parameters (dynamic_only, disabled_only, interface_filter, device) unexplained. It is adequate for basic usage but not fully complete for all filtering capabilities.

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 schema has 0% description coverage, so the description must compensate. It explains address_filter, global_only, and link_local_only, but omits device, dynamic_only, disabled_only, and interface_filter. While titles give some hints, several parameters remain underdocumented, leaving gaps.

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 clearly states the tool's function: 'Lists IPv6 addresses on the MikroTik device.' The verb 'lists' and resource 'IPv6 addresses' are specific, and the tool is distinguished from siblings like get_ipv6_address (single address) and list_ip_addresses (likely IPv4).

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 description provides filtering context (address_filter, global_only, link_local_only) but does not explicitly state when to use this tool versus alternatives like get_ipv6_address or list_ip_addresses, nor does it give exclusions. The usage is implied rather than explicit.

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