firewall_nat

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

With no annotations at all, the description carries the full behavioral burden and does the most important part: it explicitly declares 'Read-only - does not add/modify/remove rules', which substitutes for a readOnlyHint and prevents misuse. It stops short of noting the device context needed for the call or any output shape, but the key safety trait is disclosed.

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?

Two compact lines, front-loaded with verb/resource and immediately followed by the read-only caveat. No filler sentences; every clause earns its place.

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 values need no explanation, and the read-only guarantee is present. However, for a tool whose only parameter is required and undocumented, the description should at least say what device_name refers to; that omission leaves the definition incomplete.

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% and the single required parameter device_name is neither documented in the schema nor mentioned in the description. At low coverage the description is expected to compensate, and it does not, leaving the one required argument entirely unexplained.

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?

Specific verb ('List') plus a precise resource ('IPv4 firewall NAT rules') and the underlying path (/ip/firewall/nat), which cleanly separates it from sibling collection tools like firewall_filter, firewall_mangle and connection_tracking. The mention of 'chain, action, to-addresses' confirms what the listing contains.

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 read-only framing implicitly signals this is the inspection counterpart to mutating siblings such as enable_nat_rule/disable_nat_rule, but the description never names an alternative or states when to prefer it. Usage is inferable rather than stated.

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