hcloud_server_change_dns_ptr_action

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

Annotations already declare destructiveHint=true and openWorldHint=true, so the mutation/DNS-exposure risk is covered structurally. The description adds that only primary IPs are modified and that floating IPs are untouched, which is useful impact scoping, but it omits the reset/removal semantics (dns_ptr=null) and that this triggers an async Action the call may poll.

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 lines, front-loaded with the action and immediately followed by the scope constraint. The first line is largely a restatement of the title, so there is minor redundancy, but nothing is bloated.

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 nested-body action tool with 67% schema coverage and annotations carrying the safety profile, the description covers the essential scope questions an agent needs. The remaining gap is action/wait semantics and reset behavior, which is a moderate but not disqualifying omission since there is no output schema to carry return information.

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 description reinforces the key constraint that 'ip' must be one of the server's primary IPs rather than a floating IP, which is genuine added meaning over the schema's 'Single IPv4 or IPv6 address'. However, it says nothing about the 'dns_ptr' null-reset behavior or the 'wait' polling parameter, leaving those to the schema.

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 states a specific verb+resource (change reverse DNS / PTR entry for a Server) and clarifies exactly which IPs are in scope: the server's primary IPv4 and IPv6 addresses. The explicit statement that floating IPs are NOT affected also separates it from the floating-IP and primary-IP DNS variants, though it never names those siblings directly.

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 explicit when-to-use or when-not guidance and no prerequisites (permissions, ownership) are stated. The 'Floating IPs are not affected' line does give implicit routing away from hcloud_floating_ip_change_dns_ptr_action, but an agent must infer that this tool is the right one for primary-IP PTR changes on a server.

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