dns_add_record

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

With no annotations, the description carries the full burden of disclosing side effects. It does reveal that the zone is created automatically for Primary type, which is a useful behavioral trait. However, it omits other important behaviors, such as the overwrite parameter's effect, what happens when a zone doesn't exist for non-Primary types, or any permissions or rate limits.

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 extremely concise, using two short sentences to convey the core purpose and a key side effect. Every sentence earns its place, with the front-loaded action verb making the tool's function immediately clear.

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?

Despite having 7 parameters and no output schema or annotations, the description remains minimal. It fails to cover essential contextual details like return values, overwrite behavior, or handling of non-Primary zones without existing zones. For a tool with this complexity, more context is needed to guide correct invocation.

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%, with each parameter having a description. The description itself adds no additional parameter-level meaning beyond the schema, so the baseline of 3 applies.

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 ('Add a DNS record to a zone') with a specific verb and resource, and adds a distinguishing behavioral note about automatic zone creation for Primary type. This effectively differentiates it from sibling tools like dns_update_record and dns_delete_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?

The description implies usage for adding DNS records, but provides no explicit guidance on when to use this tool versus alternatives like dns_update_record or when not to use it. The note about 'Primary type' hints at a condition but doesn't clarify behavior for non-Primary zones or recommend alternative tools.

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