opn_list_nat_rules

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

No annotations provided, but description fully discloses that only MVC-managed NAT rules are returned, not legacy ones. It also describes return format (dict with 'rows' and 'rowCount'). No contradictions.

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?

Description is concise, front-loaded with purpose, and each sentence adds value. No wasted words.

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?

Covers scope, return format, and provides alternative for legacy rules. Missing parameter semantics reduces completeness slightly, but output schema exists and overall information is sufficient for most use cases.

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%, yet description does not explain the parameters 'search' or 'limit'. It does not add meaning beyond the schema's type and default values. This is a significant gap for effective use.

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?

Description clearly states it lists NAT port forwarding (DNAT) rules, using specific verb and resource. It distinguishes from sibling opn_get_config_section('nat') which returns all NAT configuration including legacy rules.

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?

Explicitly states when to use (seeing forwarded ports, checking config, troubleshooting) and when not to use (legacy rules not shown), providing alternative opn_get_config_section('nat').

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