list_nat_rules

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

Annotations already declare read-safe, idempotent, non-destructive behavior. The description adds no extra behavioral context beyond confirming the read-only nature. With rich annotations, the description offers minimal additional value, scoring adequately.

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 with a front-loaded purpose and argument documentation. No redundant sentences; every part adds value.

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 presence of an output schema (not shown) and a moderate number of siblings, the description adequately covers the tool's purpose and required parameters. It lacks details on potential limitations or output contents, but the output schema bridges that 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?

Schema description coverage is 0%, so the description compensates by explaining the tier1_id parameter as the gateway ID and the target parameter as an optional NSX Manager name with default behavior. This adds meaning beyond the schema's property titles.

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 clearly states '[READ] List NAT rules on a Tier-1 gateway,' specifying the action (list) and resource (NAT rules on a Tier-1 gateway). It distinguishes from sibling tools like create_nat_rule and delete_nat_rule by the [READ] prefix and the resource scope.

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?

No explicit guidance on when to use this tool versus alternatives like list_tier1_gateways or create_nat_rule. Usage is implied by the resource being listed, but no exclusions or situational advice are provided.

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