Update RRSet labels

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

The description goes beyond the idempotentHint annotation by disclosing that the provided label set 'replaces all existing labels.' This is a key behavioral trait for an update operation, though it does not cover edge cases like missing RRSet 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?

Two concise sentences, front-loaded with the primary purpose and enriched with one high-value disambiguation. No wasted words or repetition of schema details.

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 focused update tool with complete schema coverage and an idempotency annotation, the description is largely sufficient. It explains the operation, replacement behavior, and exclusions, though it does not mention potential prerequisites or return behavior.

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 schema already documents all parameters (100% coverage), but the description adds meaning to the labels parameter by explaining it replaces the entire existing label set. It also clarifies that records and TTL parameters are intentionally handled by other tools.

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 action: 'Update the labels of an RRSet.' It identifies the specific resource (RRSet labels) and the replacement semantics, distinguishing it from sibling tools that manage records or TTL.

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 parenthetical explicitly directs record and TTL changes to named alternatives (set_records/add_records/remove_records and change_rrset_ttl), giving clear when-not-to-use guidance and making the tool's narrow scope obvious.

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