get_nat_rules

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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description repeats this with '[READ-ONLY]', adding no new safety information. It does add useful context about the config path and the types of NAT rules contained, but it does not mention pagination, return format, or error behavior. This is similar to the calibration example where annotations cover safety, so the description adds modest but not rich 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?

Two sentences with no filler. The first sentence front-loads the core purpose, and the second provides a specific config path that adds practical value. Every sentence 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?

For a simple read-only list tool with one optional parameter, annotations already carry the safety profile and the schema fully documents the parameter. The description covers scope and config location. It does not elaborate on return values, but none are expected beyond a list of NAT rules, which is implied. Minor missing guidance about Panorama vs firewall context is more of a usage-guideline gap.

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 input schema has 100% coverage; the single 'firewall' parameter is fully described, including when it is required. The description adds no additional parameter-level detail beyond the schema, which is the expected baseline.

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 uses a specific verb plus resource: 'Retrieves all NAT policy rules', listing the three rule types (source, destination, bidirectional). It clearly differentiates from siblings like get_security_rules and get_pbf_rules by focusing on the NAT rulebase, and the config path adds additional precision.

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?

There is no explicit guidance on when to use this tool versus alternatives. Given the sibling panorama_get_device_group_nat_rules, the description should clarify that get_nat_rules is for firewall-local NAT rules rather than Panorama-based ones, but it does not. The only implied usage is 'when NAT rules are needed'.

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