Update DNS record

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

The [WRITE] tag and "Requires exact record_id" add context beyond annotations (openWorldHint, destructiveHint=false). But it doesn't disclose whether the update is partial or full replacement, what happens to fields not provided, or auth requirements. Annotations cover the safety profile but not mutation semantics.

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 sentences, front-loaded with the write tag and verb, with zero filler. Each sentence carries specific value.

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 12-param mutation tool with 17% schema coverage, no output schema, and nested objects, the description is far too thin. It omits parameter meanings, field-replacement semantics, and error/auth context that an agent needs to invoke correctly.

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 description coverage is only 17% across 12 params, with only `record_id` and `value` partially documented in the schema. The description adds no meaning about params beyond noting record_id is required — it doesn't explain ttl, cloud, usage, selector, ip_filter_mode, or upstream_https, leaving the agent to infer from names alone.

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?

States a specific verb ("Update") and resource ("an existing DNS record"), and explicitly tags it as [WRITE]. Clear enough to distinguish from siblings like create_dns_record and delete_dns_record.

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?

"Requires exact record_id" and "Read current state first" give a clear precondition (get_dns_record before updating). However, it doesn't explicitly name an alternative tool or state when-not-to-use (e.g., create vs update vs set_dns_record_cloud).

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