list_nat_gateway_rules

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

No annotations are provided, and the description only says 'List all rules'. It does not disclose behavioral traits such as pagination, default nesting depth, error handling, or the effect of filters. The schema contains details like depth and filters, but the description adds no behavioral context beyond the bare operation.

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 a single sentence, which is concise but lacks structure. It front-loads the purpose but could benefit from brevity in a structured format. It is not overly verbose but also not particularly well-organized.

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 absence of an output schema and annotations, the description should provide more complete context about the operation's results and behavior. It does not mention return format, pagination, or any edge cases. The tool has 4 parameters and nested objects, yet the description adds no richness.

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 100%, so the input schema already documents each parameter adequately. The description adds no additional meaning beyond the parameter names. With high coverage, a score of 3 is appropriate as the schema does the heavy lifting.

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 'List all rules of a specific NAT gateway', using a specific verb and resource. It distinguishes from siblings like 'list_nat_gateways' which lists gateways, and 'get_nat_gateway' which gets a single gateway. However, it does not explicitly differentiate from other rule-listing tools like 'list_firewall_rules'.

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 does not provide guidance on when to use this tool versus alternatives. There is no mention of prerequisites, limitations, or when not to use it. The required parameters imply needing a NAT gateway ID, but no explicit usage context is given.

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