Update DNS Zone RRSet

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

Annotations indicate idempotent and open world behavior. The description adds context that only labels are affected, which is behavioral information beyond annotations. However, it does not describe any side effects, permissions, or other behavioral traits.

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 extremely concise with two sentences. The first sentence states the purpose, and the second clarifies the scope by referencing dedicated tools. 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 presence of dedicated sibling tools for records and TTL (e.g., hetzner_update_zone_rrset_records, hetzner_change_zone_rrset_ttl), the description is complete. It clearly delineates the tool's responsibility and does not require additional context.

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 100%, so all parameters are documented in the input schema. The description does not add any additional parameter-specific meaning beyond what is already 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 it updates an RRSet's labels, using a specific verb and resource. It distinguishes from sibling tools by explicitly noting that records and TTL are managed via dedicated action tools.

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 that this tool should be used only for updating labels, while other aspects like records and TTL are handled by separate dedicated tools. However, it does not explicitly state when not to use this tool or provide alternatives for other use cases.

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