dnsrecon

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

The description is transparent about the active network behavior — zone transfer attempts, brute-force discovery, reverse lookups — and states what the output looks like. However, with no annotations provided, it does not disclose whether this tool is noisy or rate-limited, whether authorization/network access is expected, or any other operational side effects.

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, each with a distinct job: capabilities, use case/alternative, and output. There is no redundant restatement of the tool name or parameter schema.

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 two-parameter tool with no output schema, the description covers why to use it, when to use it, what it does, and what to expect back. It could add an explicit example or operational caveat, but nothing essential for correct invocation is missing.

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 100%, so the baseline is 3. The tool description reinforces the domain use case and lists record types, but it adds no new semantic detail beyond what the input schema already provides for domain and opts.

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?

Names a concrete resource ('DNS footprint') and enumerates the exact active actions: zone transfer attempts, brute-force subdomain discovery, reverse lookups, and DNS record enumeration. This clearly differentiates it from sibling passive discovery tools like subfinder and from network scanners like nmap.

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?

Explicitly gives the trigger condition: use when you have a domain and need to map its DNS footprint. It also provides a when-not by directing passive, multi-source subdomain discovery to subfinder.

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