gobuster_vhost

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It does disclose that the tool brute-forces Host headers and executes on a remote Kali host via SSH, which is useful context. However, it does not describe output format, potential side effects, or any safety/authorization considerations, 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 consists of two concise sentences with front-loaded purpose and no fluff. It efficiently states what the tool does and adds the operational detail of remote SSH execution without unnecessary wording.

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 has 13 parameters and no output schema, yet the description only covers high-level behavior. It omits expected return values, error handling, and operational considerations like how results are reported, making it incomplete for a complex enumeration tool.

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 structured schema already documents all 13 parameters. The description adds no additional meaning to the parameters, such as how they interact or typical values, so the baseline score of 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 tool performs virtual host enumeration by brute-forcing Host header values, which is a specific verb and resource. It also implicitly distinguishes itself from sibling modes like gobuster_dir and gobuster_dns by focusing on virtual hosts.

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 does not provide any guidance on when to use this tool versus alternatives such as gobuster_dir or gobuster_dns. It lacks explicit context about prerequisites, target scenarios, or when not to use it, so the usage is only implied by the tool's name.

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