opn_delete_nat_rule

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

Since no annotations are provided, the description fully carries the burden. It discloses savepoint protection and auto-revert in 60 seconds unless confirmed via opn_confirm_changes, and mentions the return dict format. This is good additional behavioral context.

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 extremely concise: 4 sentences, each serving a purpose. It front-loads the primary action and then adds usage guidance, behavioral note, and return info. 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?

Given the tool's simplicity (1 param, sibling tools provided), the description covers purpose, usage, behavior, and return structure. It lacks only details on error handling or permissions, but overall is very complete for a delete operation.

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 has 0% description coverage, so description must compensate. It explains that the UUID should be obtained via opn_list_nat_rules, adding meaningful context. However, it does not specify the expected format of the UUID, which would be helpful.

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 'Delete a NAT port forwarding rule by UUID with savepoint protection.' It uses specific verb (Delete) and resource (NAT rule), and distinguishes from siblings like opn_add_nat_rule and opn_update_nat_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?

Description explicitly says 'Use this when you need to remove an existing NAT rule' and advises to 'Use opn_list_nat_rules first to find the UUID.' It provides clear context but does not mention when not to use or alternative tools for modification.

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