hcloud_load_balancer_change_dns_ptr_action

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

Annotations already declare destructiveHint=true, readOnlyHint=false and openWorldHint=true, so the mutation and irreversibility profile is known. The description usefully adds scope detail — it changes PTR records for the load balancer's public IPv4 and IPv6 addresses and leaves floating IPs untouched — but says nothing about the async action returned, whether the operation is reversible, or what permissions are needed.

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 short sentences, with the core action stated first and the clarifying scope detail second. The final sentence is slightly muddled — it refers to 'the Server' rather than the Load Balancer, which reads as boilerplate carried over from a sibling tool.

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?

There is no output schema, so the description could have explained that an action object is returned and how polling with 'wait' behaves, but it does not. The scope of affected IPs is covered, yet details an agent needs before invoking a destructive async endpoint are missing.

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 67% and the nested body documents 'ip' and 'dns_ptr' including the null-reset behavior, so the schema does most of the work. The description only contributes the fact that both IPv4 and IPv6 public addresses are in scope; it adds nothing about the 'wait' flag or the required load balancer 'id'.

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 first sentence names a specific verb and resource ('Change reverse DNS entry for this Load Balancer') and the second clarifies that it alters the PTR hostname for the Load Balancer's public IPv4/IPv6 addresses. This is enough to distinguish it from the similarly named server, floating IP and primary IP DNS-PTR siblings, though the description never explicitly contrasts them.

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?

Usage is only implied: the tool is the way to set reverse DNS for a load balancer's public IPs. There is no statement of when to prefer it over hcloud_server_change_dns_ptr_action or hcloud_floating_ip_change_dns_ptr_action, no prerequisites, and no mention of how it relates to the optional 'wait' polling.

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