hcloud_list_nat_gateway_dnat_rules

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

No annotations are provided, so the description must reveal behavioral traits. It describes a read operation ('List') but omits details like pagination behavior (despite the 'limit' parameter), error handling, or authentication requirements. The description is too sparse to adequately inform an agent about side effects or limitations.

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, front-loaded sentence with no wasted words. It is concise, though it could include more context without becoming verbose. This efficiency earns a high score.

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 lack of output schema and annotations, the description should provide context about return values, error scenarios, or prerequisites. It does not explain what DNAT rules are or what the tool returns, making it incomplete for an agent to confidently invoke.

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 all parameters are documented. The description adds no extra meaning beyond what the schema provides. For high-coverage cases, baseline score is 3, and there is no additional semantic value from the description.

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 'List DNAT rules on a NAT gateway' clearly specifies the verb (List), the resource (DNAT rules), and the scope (NAT gateway). It distinguishes from sibling tools like hcloud_list_nat_gateway_snat_rules and hcloud_list_nat_gateways, which cover different resources.

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 provides no guidance on when to use this tool versus alternatives. It does not mention prerequisites, such as the existence of a NAT gateway, nor does it differentiate from other list tools in the same family.

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