opn_add_dns_override

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

With no annotations, the description fully covers behavioral traits: changes are applied immediately (Unbound reconfigured automatically), and DNS overrides cannot be auto-reverted. This allows the agent to understand the consequence of calling the tool.

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 well-structured with a summary, usage context, behavioral notes, parameter list, and return format. It is slightly verbose but every sentence adds necessary information; could be tightened without losing clarity.

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 no annotations, zero schema coverage, and presence of output schema, the description is remarkably complete. It covers purpose, usage guidelines, behavior, parameter semantics, and return format, leaving no important gaps for agent decision-making.

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 0%, but the description explains each parameter's meaning: hostname as 'e.g. 'myserver'', domain as 'e.g. 'local.lan'', server as 'IP address to resolve to (IPv4 or IPv6)', and description as optional. This adds significant value beyond the bare 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 clearly states the purpose: 'Add an Unbound DNS host override (A/AAAA record) and apply immediately.' It distinguishes from sibling tools like opn_list_dns_overrides (to check existing) and opn_delete_dns_override, making the action and resource specific.

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?

Explicitly tells when to use: 'when you need to create a local DNS record... for split-horizon DNS, internal services, or overriding external DNS.' It also advises caution: 'cannot be auto-reverted — verify settings before calling' and recommends checking existing overrides with opn_list_dns_overrides first.

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