hcloud_list_nat_gateway_dnat_rules

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

Annotations already declare readOnlyHint=true, idempotentHint=true and openWorldHint=true, so the safety profile is covered outside the description. The description adds nothing beyond that: no pagination behavior, no indication of what happens when nat_gateway_id is omitted, and no note that results may be empty.

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 front-loaded sentence with zero filler, which is appropriate sizing for a simple list tool. It is arguably under-specified rather than padded, so conciseness itself is not the weakness.

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 three-parameter read-only list tool with no output schema, the definition is minimally viable but leaves real gaps: pagination via limit, whether nat_gateway_id is optional or effectively required, and the shape of returned rules are all unstated.

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 baseline is 3; the schema already documents region, nat_gateway_id and limit, albeit with one-word labels. The description adds no meaning beyond the schema, for example whether nat_gateway_id acts as a filter or is effectively required despite being optional.

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 plus resource: 'List DNAT rules on a NAT gateway'. The DNAT qualifier implicitly separates it from hcloud_list_nat_gateway_snat_rules, so an agent can distinguish it from nearby siblings without opening the schema, though no sibling is named explicitly.

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 prerequisites, and no pointer to alternatives such as hcloud_list_nat_gateway_snat_rules or hcloud_show_nat_gateway. The agent must infer usage entirely from the tool name.

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