opnsense_dns_blocklist_set

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

No annotations provided, so the description carries the burden. It explains the tool modifies configuration, requires confirmation, and requires a follow-up apply. It could elaborate on merge vs replace behavior, but is sufficient.

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?

Three sentences: first states purpose and parameters, second gives critical follow-up instruction, third is a warning. No redundant information, front-loaded.

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 output schema and siblings that retrieve data, the description provides necessary context: how to discover source IDs via another tool, the need for apply, and destructive nature. Minor gap: whether changes replace or merge existing config, but overall complete.

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 100%, but the description adds significant value by explaining parameter usage (e.g., 'enable/disable' for enabled, cross-reference to opnsense_dns_blocklist_sources_list for sources, and clarifying that confirm must be true).

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 tool updates Unbound DNSBL configuration, listing specific actions like enable/disable, select sources, set URLs, configure NXDOMAIN. This distinguishes it from sibling read tools like opnsense_dns_blocklist_get.

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 explicitly says to call opnsense_dns_apply after to activate, and warns 'DESTRUCTIVE: requires explicit confirmation.' It does not contrast with alternatives, but the purpose is clear enough.

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