hcloud_list_nat_gateways

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 that. It does not disclose pagination behavior tied to limit, whether results are region-scoped, or how many gateways are typically returned.

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?

Three words with zero waste and nothing to trim, but the brevity comes from under-specification rather than disciplined editing. There is no structure to front-load because there is no content.

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 simple read-only list tool with full schema coverage, annotations, and no output schema, the minimal description is not disqualifying. Still, nothing tells the agent that region is mandatory to avoid an error, which is the one thing a caller most needs.

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 both the required region and the optional limit are documented in the schema itself, establishing the baseline of 3. The description contributes no additional meaning about parameter semantics, but the schema already carries that burden.

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?

"List NAT gateways" merely expands the tool name hcloud_list_nat_gateways into prose; it is a tautological restatement rather than a distinct statement of what the tool returns or its scope. It gives no differentiation from siblings such as hcloud_show_nat_gateway or hcloud_list_nat_gateway_snat_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?

There is no when-to-use guidance, no mention of the required region scoping, and no pointer to alternatives like hcloud_show_nat_gateway for single-gateway lookup or the SNAT/DNAT rule listers. An agent must infer everything about selection from the name alone.

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