opn_add_icmpv6_rules

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

Despite no annotations, the description fully discloses the behavioral traits: creation of 5 rules per RFC 4890, savepoint protection with auto-revert, and the return structure. This provides an agent with a clear understanding of what happens when the tool is invoked.

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 well-structured and front-loaded: it immediately states the purpose, then explains usage context, lists the specific rules, and finishes with parameters and return value. Every sentence adds value.

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?

Given the tool's complexity (5 rules, savepoint mechanism), the description provides a comprehensive overview, including the specific rules, the savepoint protection, and the return value structure. It is fully sufficient for an AI agent to use 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?

The description provides clear semantics for the single parameter 'interface', including examples and default value ('lan'), compensating for the 0% schema coverage. It is concise and informative.

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 uses a specific verb ('Create') and resource ('essential ICMPv6 firewall rules required for IPv6 operation'), and clearly distinguishes from sibling tools like opn_add_firewall_rule by specifying ICMPv6 and the specific rules per RFC 4890.

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 explicit usage context ('when setting up IPv6 on an interface') and explains the necessity, but does not explicitly state when not to use it or mention alternative tools, though the specialization is clear.

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