Update DNS record

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

The description adds value beyond annotations by explaining the partial update behavior and the special response field 'resolved_domain' when domain is provided. Annotations already indicate non-destructive and idempotent hints, which are consistent. No contradictions found.

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 only three sentences, each conveying important information without redundancy. It is front-loaded with the core action and efficiently adds details about partial update and a specific response behavior. No wasted words.

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 has 7 parameters and no output schema, the description covers the partial update behavior and a specific output field, but does not mention error cases, response format for other fields, or what happens if no optional fields are provided. Adequate but has gaps.

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 100%, so the schema already documents all parameters well. The description adds only a general note about partial update and resolved_domain, but does not provide additional semantics for individual parameters. Baseline score of 3 is appropriate.

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 that this tool performs a partial update of a DNS record, specifying that only sent fields are overwritten while omitted fields retain current settings. The title 'Update DNS record' and the sibling tools (create, delete) make its purpose distinct.

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 when you want to update only specific fields of a DNS record, as it performs a partial update. However, it does not explicitly state when not to use it or compare it to other tools like create_dns_record. Missing explicit alternatives guidance.

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