opn_remove_dnsbl_allowlist

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

With no annotations, the description carries the full burden. It states that changes are applied immediately and describes the return dict with 'removed', 'not_found', 'dnsbl_status', and 'service_status'. It does not mention authentication or rate limits, but covers the essential behavioral aspects of the operation.

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 no unnecessary words. It follows a logical structure: purpose, usage context, prerequisite, parameter list, and return value. The key information is 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 the tool's simplicity (2 parameters), the description covers all necessary aspects: purpose, usage scenario, parameter details, and return format. The presence of an output schema doesn't reduce the need for completeness, and the description adequately covers the return values.

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 explains the uuid as 'blocklist UUID from opn_list_dnsbl' and the domains parameter as 'comma or newline-separated', adding meaningful detail beyond the raw schema types.

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 'Remove domains from a DNSBL allowlist', specifying the verb 'Remove' and the resource 'domains from a DNSBL allowlist'. This distinguishes it from siblings like opn_add_dnsbl_allowlist and opn_update_dnsbl.

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 states when to use the tool: 'when you no longer need a domain allowlisted and want to re-enable DNSBL blocking for it.' It also provides a prerequisite by referencing opn_list_dnsbl to get the UUID. It does not explicitly mention when not to use it, but the guidance is clear enough.

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