theharvester_dns_brute

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

No annotations are provided, so the description bears full responsibility. It states the action and method (DNS brute force with wordlist) but omits important behavioral details such as potential network impact, duration, rate limits, or required permissions. This lack of transparency could mislead an agent about the tool's implications.

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, concise sentence that front-loads the action and purpose. Every word contributes value; there is no redundancy or fluff.

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 two parameters and no output schema, the description is minimally adequate. It states the purpose but does not clarify the output format, default wordlist behavior, or potential side effects. Given the simplicity, it could be more complete but is not severely lacking.

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 input schema descriptions cover both parameters (domain and dns_server) fully, achieving high schema coverage. The tool description adds the context of using a wordlist, but no additional semantic value beyond what the schema provides. Baseline 3 is appropriate.

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 verb (Perform), resource (DNS brute force enumeration), and purpose (discover subdomains using a wordlist). It distinguishes itself from sibling tools by specifying DNS brute force for subdomain discovery, unlike others focused on search, emails, or full recon.

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 implies usage for discovering subdomains but does not provide explicit guidance on when to use this tool versus alternatives, nor does it mention conditions or prerequisites. Usage is implied but not clearly differentiated.

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