opn_get_dnsbl

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

No annotations are provided, so the description must convey behavioral traits. It indicates a read operation ('Get') and lists return fields, implying no side effects. However, it does not disclose permissions, rate limits, or potential errors. The description adds some context beyond the name but lacks depth.

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, consisting of three short sentences and a bulleted list. The first sentence states the purpose, followed by usage guidance and return structure. Every sentence adds value without redundancy.

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 has only one required parameter and an output schema (mentioned but not provided), the description covers the purpose, usage context, prerequisite, and return fields. It doesn't discuss error handling or authentication, but for a straightforward read operation, it is largely 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?

The sole parameter 'uuid' is not described in the input schema (0% coverage), but the description explicitly states 'by UUID' and instructs to fetch the UUID from 'opn_list_dnsbl first'. This adds significant meaning beyond the raw schema, explaining how to obtain and use the parameter.

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 retrieves the full DNSBL configuration for a specific blocklist by UUID. It specifies the action ('Get'), the resource ('DNSBL configuration'), and the identifier needed. It also distinguishes from the sibling tool 'opn_list_dnsbl' by mentioning it as a prerequisite.

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 tells when to use the tool: 'when you need to see all available providers and their selection state' and similar. It also instructs to 'Get the UUID from opn_list_dnsbl first,' providing a clear prerequisite. However, it does not explicitly state when not to use or mention alternative tools.

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