opn_delete_dns_override

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

With no annotations provided, the description fully carries the behavioral burden. It states the deletion is applied immediately, Unbound is reconfigured automatically, and changes cannot be auto-reverted. It also describes the return value structure, which adds transparency beyond the bare action.

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 concise with three sentences, each serving a purpose: action, effect, warning/prerequisite, and return. No superfluous words, but could be slightly more structured.

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 delete tool with one parameter, the description covers the essential aspects: what it does, the immediate effect, prerequisites, and return format. It is nearly complete but lacks details on error handling or UUID format.

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 0%, so the description must compensate. It mentions 'by UUID' but provides no format, example, or explanation of what constitutes a valid UUID for the uuid parameter. The description adds minimal value over 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 clearly states the action 'Delete an Unbound DNS host override by UUID' and specifies the resource (DNS host override) and method (by UUID). It is distinct from sibling tools like opn_add_dns_override and opn_update_dns_override.

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 provides a prerequisite: 'Use opn_list_dns_overrides first to find the UUID.' It also warns about irreversibility and to verify UUID before calling. It does not explicitly mention when to avoid the tool, but the context is clear enough.

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