hcloud_list_nat_gateway_snat_rules

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

The description lacks any behavioral information beyond the action. It does not disclose read-only nature, pagination, permissions, or limits. With no annotations, the description should provide more context about behavior.

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 sentence, concise and front-loaded. It communicates the core function without unnecessary words, but could be slightly more informative without losing conciseness.

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?

With 3 parameters, no output schema, and no annotations, the description is minimal. It does not explain return format, defaults, or behavior under various conditions. The tool is simple, but more context (e.g., lists all rules, pagination) would be helpful.

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 coverage is 100%, so parameters are already documented. The description adds no extra meaning beyond the tool's purpose. Baseline score of 3 is appropriate as the description does not enrich parameter understanding.

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 clearly states the action ('List'), the resource ('SNAT rules'), and the context ('on a NAT gateway'). It distinguishes this tool from siblings like hcloud_list_nat_gateway_dnat_rules (for DNAT rules) and hcloud_show_nat_gateway (for gateway details).

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?

No guidance is provided on when to use this tool vs. alternatives. It does not mention prerequisites, when not to use it, or that it should be used for listing SNAT rules specifically, which is implied but not explicit.

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