bb_subdomain

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

The description reveals it uses DNS batch resolution and custom dictionary, giving some behavioral insight. It implies concurrent requests via the parameter. However, it does not disclose potential impacts (e.g., DNS query rate limiting, wildcard handling, or authentication requirements). With no annotations, more detail is needed.

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 extremely short (one phrase), which is concise but lacks structure. It front-loads the core purpose but omits any sentences about usage, behavior, or output. It could be more informative without losing conciseness.

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 4 parameters, 0% schema descriptions, and an existing output schema, the description is incomplete. It does not explain return values, prerequisites, or how to interpret results. The context of sibling security tools demands more detail for correct usage.

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%, so the description should explain parameters. It mentions 'DNS batch resolution' and 'custom dictionary' which partially cover domain and wordlist, but ignores auth_token and concurrent. Parameter semantics are weak and rely heavily on naming.

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 performs subdomain enumeration using DNS batch resolution and custom dictionary. It specifies the resource (subdomains) and method (DNS), distinguishing it from sibling tools like bb_dir_scan or bb_port_scan. However, it lacks detail on the output format or scope.

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 guidance on when to use this tool versus alternatives like bb_takeover or bb_secrets. It does not mention prerequisites, limitations, or scenarios where it is appropriate. The sibling list shows many similar tools but no comparative information.

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