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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only says 'check' without revealing the operation's nature: whether it performs a live DNS query, returns a single boolean or per-list results, or has any side effects or rate limits. The description is too thin to set accurate expectations.

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 a single compact sentence with the main topic front-loaded, and it contains no wasted words. However, the telegraphic style omits essential details, making it under-specification rather than effective conciseness.

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?

For a tool with one optional parameter, no annotations, and an output schema that is not shown, the description should state what 'q' represents and what a successful check returns. It does neither, leaving critical usage details unresolved despite the overall low complexity.

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% and the description does not explain the sole parameter 'q'. The default of an empty string adds further ambiguity. An agent cannot infer the expected input format from the description, despite the blocklist names being explicit.

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?

States a specific verb 'check' and resource 'DNS Blocklist' while naming four concrete blocklists (Spamhaus, Barracuda, SORBS, SpamCop), which distinguishes it from generic DNS tools like dnsquery or reversedns. However, it never clarifies whether the input should be an IP address, a domain, or both, and the meaning of 'q' remains implicit.

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?

No guidance is given on when to use this tool versus alternatives. There is no mention of when to prefer dnsbl over spamhauslookup (which likely covers one of the same lists) or other DNS/blocklist siblings, and no exclusions, prerequisites, or context are provided.

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