disable_ipv6_firewall_rule

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: it discloses the MIKROTIK_ALLOW_WRITE=true gate, the two-phase confirm preview/apply behavior, the specific error cases (AmbiguousResourceError, no match, disabled ipv6 package), and the no-creation guarantee.

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/resource and command, then behavior. Slightly verbose with a couple of redundant 'Errors clearly' clauses, but nearly every sentence carries actionable information.

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 mutation tool with an output schema already covering return values, the description supplies everything needed: precondition (write flag), safety flow (confirm), resolution semantics, and error conditions. Nothing material 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; it explains comment (resolution key), chain (optional narrowing when comments collide), and confirm (preview vs. apply). device_name is left implicit, which is a minor 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 (disable) and resource (an EXISTING IPv6 firewall filter rule), and names the exact underlying command. It distinguishes itself from siblings by noting it mirrors disable_firewall_rule on the IPv6 menu and contrasts with enable_ipv6_firewall_rule.

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?

Clear context for use, including the confirm=False preview-then-confirm=True workflow and the never-creates guarantee. The alternative for re-enabling is named, but it doesn't broadly explain when to prefer this over other remediation tools.

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