opn_reconfigure_unbound

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

Discloses that it restarts Unbound, changes take effect immediately, and cannot be auto-reverted. Also mentions return type. Could add detail on whether operation is blocking, but overall very informative.

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?

Four sentences, front-loaded with main action, then context, caution, and return type. No redundant words.

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 zero parameters and simple tool, description fully covers purpose, usage context, behavioral notes, and return value. Output schema exists but not needed.

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?

No parameters, so baseline 4. Description does not need to add parameter info.

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?

Clearly states the action 'Apply pending Unbound DNS resolver configuration changes' and resource 'Unbound DNS resolver'. Distinguishes from sibling reconfigure tools for other services (ddclient, dnsmasq, haproxy).

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 to use after making DNS configuration changes (adding overrides, forward zones) and warns about the lack of savepoint protection and immediate effect. Provides a clear when-to-use and caution.

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