gobuster_dns

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

With no annotations, the description bears the full burden of behavioral disclosure. It reveals that the tool executes on a remote Kali host via SSH and uses wordlist-based brute forcing, which are meaningful traits. However, it omits side effects, async scan behavior, result output, and potential rate-limit impact, leaving significant gaps.

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 two sentences long and front-loads the essential purpose. Every word earns its place, with no filler or repetition of schema details.

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's complexity (10 parameters) and lack of output schema, the description is too sparse. It fails to mention return values, async/sync behavior, scan lifecycle (e.g., using gobuster_status), or how to interpret results. These are critical for an agent to correctly invoke the tool and use its output.

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 coverage is 100%, so every parameter has a description. The tool description adds minimal semantics beyond the schema, only framing the operation as 'wordlist-based brute forcing'. It does not elaborate on how parameters interact or provide usage examples, fitting the baseline 3.

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 it is the 'DNS subdomain enumeration mode' and specifies the verb 'discovers' with the resource 'subdomains for a target domain'. This unambiguously differentiates it from sibling tools like gobuster_dir (directory brute-forcing) and gobuster_vhost (virtual host discovery).

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 phrase 'DNS subdomain enumeration mode' implies the tool is for discovering DNS subdomains, which guides selection among the gobuster family. It also notes remote execution via SSH, giving context. However, it does not explicitly state when NOT to use it or name alternative tools, so it falls short of a 5.

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