list_nat_rules

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

Annotations already indicate read-only, idempotent, non-destructive. Description adds [READ] marker, notes truncation ('check truncated'), and clarifies scope (USER section only), going beyond annotations.

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?

Compact and well-organized, with a clear [READ] header, prerequisites, usage scenarios, and param explanations. Every sentence 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 2 simple params and no output schema, description covers purpose, prerequisites, usage, truncation hint, and scope. Annotations complement with safety profile. Adequately complete.

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?

With 0% schema coverage, description explains tier1_id as 'Gateway ID, as returned by list_tier1_gateways' and target as 'NSX Manager target from config (default if omitted)'. Adds meaning but target description could be more specific.

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?

Describes listing NAT rules on a Tier-1 gateway, specifying the USER section and noting it excludes NSX-internal NAT. Clear verb+resource and 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?

Explicitly states prerequisite (get tier1_id from list_tier1_gateways) and provides specific use cases: before create_nat_rule to avoid id clash and before delete_nat_rule to confirm rule behavior.

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