ncloud_list_nat_gateways

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

Annotations declare readOnlyHint=true, and the description's 'List' is consistent with a safe read operation. The description adds useful context by specifying the scope as 'current region' and noting that it lists all instances. This goes beyond the annotation but does not describe pagination or return format, making it slightly above average.

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, clean sentence that conveys the essential purpose without any unnecessary words or repetition. It is front-loaded with the verb and resource, making it highly scannable.

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?

While the schema documents all parameters, the description gives no information about pagination behavior, default result size, response structure (no output schema exists), or whether filters are optional. This is adequate for a simple list tool but leaves gaps for an agent unfamiliar with NAT Gateway APIs.

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%, with each of the 13 parameters fully documented in the schema. The description itself adds no parameter-specific details beyond what the schema already provides, so the baseline score of 3 applies.

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 (List) and clear resource (NAT Gateway instances) with a defined scope (current region). This clearly distinguishes it from sibling tools like ncloud_get_nat_gateway_detail, which fetches a single instance, and from create/delete/set tools.

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 implies the tool is for listing all NAT Gateways, but it does not explicitly state when to choose this over alternatives like ncloud_get_nat_gateway_detail or provide exclusion criteria. The intended use case is reasonably clear from the name and description, but no explicit guidance is given.

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