disable_mangle_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 write guard (env var gate), the default confirm=False preview vs confirm=True apply behavior, the 'never creates a rule' guarantee, and the exact error conditions (no match, or AmbiguousResourceError on multiple matches). That is well beyond what the schema provides.

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 action and the resolution key, then the guard, then the confirm flow. The parenthetical RouterOS command adds concrete context rather than filler, though the paragraph structure is slightly rambling compared to a tight two-sentence form.

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 an output schema exists, return values need not be described. The remaining obligations for a guarded write tool — preconditions, confirmation protocol, ambiguity errors, and the no-create guarantee — are all present, so an agent can call it correctly without further discovery.

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 (the resolution key), chain (optional narrowing of the match), and confirm (preview vs apply). device_name is left unexplained, which is the only gap, but the semantics of the risky parameters are fully covered.

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 ('Disable an EXISTING firewall mangle rule'), gives the underlying RouterOS command, and explicitly distinguishes itself from its counterpart 'enable_mangle_rule' and from creation behavior. An agent can pick it out of the large sibling list immediately.

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 usage context: it operates on an existing rule resolved by comment, may be narrowed by chain, and carries the explicit 'blocked unless MIKROTIK_ALLOW_WRITE=true' precondition plus a two-step confirm flow. It does not spell out when to prefer it over e.g. disable_firewall_rule or disable_nat_rule, but the domain is unambiguous.

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