hcloud_show_nat_gateway

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

No annotations are provided, so the description carries full burden. It only states 'Get details' without disclosing any behavioral traits such as read-only, authentication requirements, rate limits, or what happens (e.g., returns full object structure). This is insufficient for a tool with no annotations.

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 very short and front-loaded, with no wasted words. However, it is overly minimal and could benefit from a bit more context without sacrificing 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?

For a simple show tool with 2 required parameters and no output schema, the description provides the basic purpose but lacks details on return value structure, constraints, or any error scenarios. It is adequate but not complete.

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?

Parameter schema coverage is 100%, with the schema already describing 'Region' and 'NAT gateway ID'. The description does not add any additional meaning beyond the schema, so it meets the baseline of 3.

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?

Description 'Get details of a specific NAT gateway' uses a specific verb ('Get details') and clearly identifies the resource (NAT gateway) and scope ('specific'). It clearly distinguishes from sibling tool hcloud_list_nat_gateways which lists all gateways.

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 implies use when you have a specific NAT gateway ID, but it does not explicitly state when to use this tool versus alternatives (e.g., list or other show tools), nor does it provide when-not-to-use or prerequisite information.

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