Change Server Reverse DNS

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

Annotations list idempotentHint=true, non-destructive, non-read-only. The description adds the reset behavior (setting to null). However, it does not disclose other behavioral traits like potential errors, prerequisites, or effects. With annotations present, it adds modest value.

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 two sentences, front-loaded with the main action, and includes a specific usage note. No extraneous information.

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?

Given the tool's simplicity and the presence of annotations and full schema, the description is mostly complete. It lacks mention of prerequisites (server existence, IP assignment) and success behavior, but these are minor for a simple mutation.

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?

All parameters have descriptions in the schema (100% coverage). The description's role is to add meaning beyond the schema, but it largely restates the same info (e.g., 'change reverse DNS', 'set to null to reset'). No new semantic details are provided.

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 tool's purpose: changing reverse DNS for a server's IP address. It specifies 'one of a server's public IPv4 or IPv6 addresses', which distinguishes it from sibling tools like hetzner_change_floating_ip_rdns that target floating IPs. The reset behavior is also mentioned.

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 provides when to use by specifying 'server's public...' but does not explicitly contrast with alternatives like other RDNS change tools. It gives a usage example (set to null to reset), but lacks guidance on prerequisites or conditions.

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