hcloud_primary_ip_change_dns_ptr_action

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

Annotations already declare a destructive, non-read-only mutation. The description adds no behavioral context such as what existing PTR data is replaced, auth requirements, or the effect of null values, and does not mention the wait/polling 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 first sentence front-loads the purpose, but the second and third sentences largely repeat the same idea without adding useful detail. It is short, but not every sentence earns its place.

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 destructive action with a nested request body and no output schema, the description does not explain the resulting action, polling behavior, or how null dns_ptr resets differ between IPv4 and IPv6. The schema and annotations carry most of the missing context, leaving the description incomplete.

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?

The description mentions no parameters, and schema description coverage is only 67%, so it does not compensate for the undocumented portions. The schema itself describes id, body.ip, body.dns_ptr, and wait, but the description adds no meaning beyond that.

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 and resource: changing reverse DNS/PTR records for a Primary IP. Naming the Primary IP resource distinguishes it from the floating IP and server change-DNS siblings, though it does not explicitly compare itself to 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?

The description only restates the capability and gives no guidance on when to use this action versus alternatives, nor any prerequisites or exclusions. The intended use is implied by the name, but not explained in the description.

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