gobuster_vhost

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

With no annotations, the description fails to disclose core behavioral traits such as it being a network-scanning tool that may be slow or loud, or whether it writes output. It only provides minimal parameter hints.

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 brief and front-loaded with the purpose, but the parameter list is a bit terse and omits 'threads' entirely; still, no wasteful prose.

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?

The tool lacks an output schema and annotations, placing the burden on the description; it does not address output format, expected duration, prerequisites (e.g., URL must be reachable), or how to interpret results.

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 0%, so the description must explain all parameters, but it omits 'threads' entirely and gives only shallow explanations for the other three (e.g., 'auto-selects if empty' without detail).

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 'Virtual host discovery using Gobuster', identifying a specific action (discovery) and resource (virtual hosts). This differentiates it from sibling tools like gobuster_dir or gobuster_dns.

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 offers no guidance on when to prefer this tool over alternatives; there is no mention of use cases or comparison with gobuster_dir, gobuster_dns, or ffuf_fuzz.

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