hcloud_list_nat_gateway_snat_rules

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint, so the safety profile is covered. The description adds nothing beyond them — no pagination behavior, no default limit, no indication of what happens when nat_gateway_id is absent despite being optional.

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?

A single short sentence with no filler and the resource front-loaded. It is efficient, though the terseness edges into under-specification rather than tight clarity.

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 list tool with no output schema, the description should at least clarify the optional scoping parameter and result/pagination expectations. It leaves the ambiguity around nat_gateway_id being optional in a tool described as operating 'on a NAT gateway' entirely unresolved.

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 three parameters are already documented, albeit tersely ('Region', 'Max results', 'NAT gateway ID'). The description adds no format, default, or scoping semantics, so the baseline 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?

States a specific verb ('List') and resource ('SNAT rules on a NAT gateway'), which implicitly separates it from hcloud_list_nat_gateway_dnat_rules and hcloud_list_nat_gateways. It never names those siblings explicitly, so differentiation relies on the agent inferring from the noun.

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 guidance on when to use this versus listing gateways or DNAT rules, no mention that region is mandatory, and no note about whether nat_gateway_id may be omitted to list across all gateways. The reader must fall back entirely on the schema.

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