opnsense_dns_blocklist_set

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

With no annotations, the description carries full burden. It correctly labels the tool as destructive and requires confirmation, and notes that changes are pending until apply. This is good context for a config update 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?

Two sentences, front-loaded with action items, and a crucial follow-up instruction. No wasted 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 schema covers all parameters with descriptions, the description adds the apply dependency and destructive warning, which is sufficient. No output schema, but typical for a set tool.

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%, and each parameter is described. The description adds value by suggesting use of opnsense_dns_blocklist_sources_list to discover source IDs, which is extra guidance beyond 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 tool updates Unbound DNSBL configuration, listing specific actions (enable/disable, source selection, custom URLs, NXDOMAIN mode). It distinguishes from siblings like get/list tools by being the write operation.

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 instructs to call opnsense_dns_apply after this tool to activate changes, providing clear follow-up guidance. The DESTRUCTIVE label and confirm requirement indicate careful usage, but no explicit alternatives or when-not cases are stated.

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