nat_port_forwards

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

No annotations are provided, so the '[READ]' prefix in the description carries the transparency burden and appropriately signals this is a safe read-only operation. However, beyond labeling it as READ, the description doesn't disclose what 'normalized' means (e.g., how the data is transformed) or whether the output lacks certain raw fields, which would be useful behavioral context for an agent.

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?

The description is concise at three sentences with zero waste. It front-loads the purpose and READ qualifier, then documents the parameter. Efficient and well-structured.

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?

This is a simple single-parameter read tool with no output schema and no annotations. Given the complexity, the description covers the basics: purpose, read-only nature, and parameter semantics. However, without an output schema or annotations, the description could have clarified what the 'normalized' output looks like, since an agent receiving results needs to interpret them without any return-format documentation.

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?

The single parameter 'target' is documented in the description ('Firewall target name from config; omit for the default'), which is clear and adds meaning beyond the bare schema. However, schema description coverage is 0% for the parameter properties, so the description is the only source, and while it explains the parameter well, it doesn't explain possible values or how to discover valid firewall target names.

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?

The description states 'Inbound port-forward (DNAT) rules, normalized' which is a specific verb+resource pair. It clearly identifies the purpose (reading inbound port-forward rules) and the '[READ]' prefix signals this is a read operation. However, it doesn't explicitly distinguish from sibling NAT tools like nat_outbound and nat_one_to_one, which are close alternatives.

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 description provides some context by labeling it as inbound DNAT rules, which implies it's for reading port forwards. However, no explicit when-to-use vs when-not-to-use guidance is given, and it doesn't reference the sibling NAT tools (nat_outbound, nat_one_to_one) that might be confused with it.

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