ipv6_firewall_filter

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

With no annotations, the description carries the full burden and does meaningful work: it declares the operation read-only and explicitly says it does not add/modify/remove rules, and it discloses the non-obvious edge case that a disabled `ipv6` package yields an empty list rather than an error. It stops short of describing pagination or return shape, but the safety profile and the key quirk are covered.

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 verb and resource, followed by the sibling mapping, the read-only guarantee, and the empty-list edge case. Every sentence adds distinct information with no filler.

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-value details need not be spelled out, and the description still volunteers the most important output behavior (empty list vs. error). For a single-parameter read tool this is fully sufficient to call 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 description coverage is 0% for the single `device_name` parameter, and the description adds no syntax, format, or sourcing guidance for it. The parameter name is largely self-explanatory, so the gap is not severe, but the description does not compensate for the coverage deficit.

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 and resource ('List IPv6 firewall filter rules') and explicitly names the sibling it parallels ('Mirrors `firewall_filter` for IPv6'), letting an agent distinguish it from the IPv4 version and from the ipv6_* mutators without opening a 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?

The tool's context is clear from 'Mirrors `firewall_filter` for IPv6', which tells the agent when to pick this over the IPv4 sibling. There is no explicit when-not guidance or mention of the enable/disable_ipv6_firewall_rule siblings that mutate the same ruleset, so it falls short of a full routing statement.

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