Change a DNS record

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

The description adds substantial context beyond the annotations: set is a full replacement, remove deletes matching records, propagation usually takes minutes, and user approval should be obtained before remove. This meaningfully expands on destructiveHint=true and idempotentHint=false.

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 front-loaded with purpose, then action semantics, type notes, alternative tool, auth, propagation, and approval guidance. Every sentence carries useful information, with no filler.

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 destructive DNS mutation with eight parameters, the description covers the essential invocation semantics, auth constraints, propagation expectations, and the key alternative tool. The remaining details, such as confirm and TTL, are already documented in the schema.

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 high, but the description adds real meaning for the action enum by explaining set/add/remove behavior and clarifies record-matching semantics for remove. It also explains redirect type variants, though TTL and priority are left entirely to the schema.

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 opens with a specific verb and resource: 'Change one DNS record of a domain bought on Lizard.' It clearly distinguishes this from domain_attach by saying that pointing a name at a Lizard app should use domain_attach instead.

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?

It explains the three actions explicitly: set replaces matching records, add keeps others, and remove deletes matching records. It also gives the key alternative for Lizard apps and states that a signed-in user is required, with API keys limited to reading.

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