opn_update_dns_override

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

No annotations provided, so description carries burden. Discloses immediate application (Unbound reconfigured), preservation of non-provided parameters, non-revertability, and return structure. Does not cover error handling or authentication.

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?

Well-structured: header, usage context, immediate effect warning, parameter list, return info. Each sentence adds value. No fluff.

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 6 params with 0% schema coverage, description covers parameters, usage, and return. Lacks error cases (e.g., missing UUID) and explicit mention of override type. Good overall.

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 description must compensate. Lists all 6 parameters with explanations and examples (e.g., 'e.g. myserver', 'IPv4 or IPv6'). Adds meaning beyond bare schema types. Could improve with format constraints.

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 'Update an Unbound DNS host override by UUID', specifying the verb (update), resource (DNS host override), and method (by UUID). It distinguishes from sibling tools like add and delete.

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 says when to use (to change properties), recommends using opn_list_dns_overrides first to get UUID, and warns that changes cannot be auto-reverted. Lacks mention of alternatives like add/delete but is clear overall.

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