add_dns_record

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

With no annotations provided, the description carries full behavioral burden and excels: it states records are added without replacing existing ones, and warns that individual records cannot be deleted. The note about delete_domain removing all records is a clear, honest caveat about consequences.

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 sentences, front-loaded with the core action, then type guidance, then an important destructive caveat. Every sentence earns its place and there is no redundancy.

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 simple add operation with no output schema, the description covers the key prerequisites, type semantics, add-only behavior, and deletion limitations. It lacks an explicit pointer to the add_acme_challenge sibling for ACME-specific use cases, but overall the tool can be called correctly from this description alone.

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?

Input schema coverage is 100%, so the baseline is 3, but the description adds valuable semantic meaning for the type parameter by explaining what values are appropriate for IPs, hostnames, and TXT strings. This supplements the schema rather than merely repeating it.

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 defines the action as adding a DNS record to a subdomain the user owns, and specifies the record types A, AAAA, CNAME, and TXT. This distinguishes it from sibling tools like delete_domain and add_acme_challenge.

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 gives explicit guidance on what each record type is for, which serves as strong usage direction. However, it does not explicitly compare itself to the similarly named add_acme_challenge or state when not to use this tool.

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