vhost_enum

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

With no annotations, the description must fully disclose behavioral traits. It mentions the prerequisite that the target must be in scope and describes the return structure, but does not discuss potential side effects such as high request volume or noise. This is adequate but not rich, warranting a 3.

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 front-loaded with a concise one-liner and then organized into structured metadata sections. There is some redundancy between the initial line, USECASE, and INPUT_DESCRIPTION, but the additional instructions, prerequisites, and examples are valuable, so it remains appropriately concise.

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 description covers purpose, instructions, prerequisites, an example invocation, and the output structure (status, discovered vhosts, command, mode). With an output schema and three parameters, this is complete enough for an agent to select and invoke the tool correctly.

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 0%, but the description thoroughly explains each parameter: target as the base URL, domain as the apex domain for vhost candidates, and wordlist as optional with a default. This adds complete meaning beyond the bare schema types.

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's function: 'Brute-force virtual hosts on a web server (gobuster vhost mode).' This specifies the verb, resource, and method, and distinguishes it from sibling tools like subdomain_enum and dir_bruteforce through the focus on 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 description provides clear context: 'Discover name-based virtual hosts served by an in-scope web server' and includes prerequisites and related tools. However, it does not explicitly state when not to use this tool or when to prefer a related tool like subdomain_enum, so it lacks direct exclusions.

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