gobuster_dns

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

With no annotations, the description carries the full burden. It discloses helpful behaviors: wordlist auto-selection when empty, and show_ips affecting IP address output. However, it omits critical details such as return format, network impact/noise, or concurrency behavior, leaving some important traits undisclosed.

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?

Exceptionally concise and well-structured. The main purpose occupies the first line, followed by a clean parameter list. Every sentence adds value with no filler or repetition.

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?

This tool has 4 parameters, no output schema, and no annotations. The description gives a basic summary but is incomplete: it fails to explain the threads parameter, what the result looks like, or any operational caveats (e.g., speed, DNS resolution behavior). Given the tool's complexity, more context is needed for a minimal viable description.

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 description explains three of four parameters: domain (with example), wordlist (with auto-select behavior), and show_ips (with meaning). It completely omits 'threads', and because schema description coverage is 0%, the description must compensate for all parameters. It partially does, but the threads gap is significant.

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 opens with a clear, specific statement: 'DNS subdomain brute-force using Gobuster.' This identifies the verb (brute-force), resource (DNS subdomains), and tool (Gobuster), and distinguishes it from sibling tools like gobuster_dir and gobuster_vhost.

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 explicit guidance on when to use this tool vs. alternatives like subfinder_enumerate or dig_lookup. It implies active brute-force through the wordlist parameter, but it never states when to choose this over passive enumeration or when not to use it.

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