dns_subdomain_enum

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

With no annotations available, the description carries the full burden. It discloses meaningful behavioral traits: the use of crt.sh for passive CT lookups, active DNS brute-force, result deduplication, and resolution of discovered subdomains to IP addresses. It does not mention potential rate limits, time costs, or failure modes, but it covers the core behavior well.

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, front-loaded with the core action and purpose. Every sentence earns its place: the first defines the methods, the second adds deduplication and resolution behavior. No filler or redundancy.

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 no output schema and no annotations, the description does a solid job: it explains what the tool does, how it works, and implies the return value (subdomains with IP addresses). It could additionally mention default limits or error behavior, but for a subdomain enumeration tool with well-documented parameters, this is sufficiently complete.

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 the baseline is 3. The description adds some context by connecting CT lookups to the use_ct parameter and brute-force to the wordlist parameter, but it does not provide additional detail beyond the schema for limit or domain. Overall, it complements the schema without adding significant new semantic depth.

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 uses a specific verb 'Enumerate subdomains' and clearly identifies the resource (subdomains of a target domain). It distinguishes this tool from siblings like 'dns_lookup' or 'ct_search' by explicitly stating the combined passive CT and active brute-force approach, along with deduplication and IP resolution.

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?

Although it does not explicitly name alternatives or state when-not-to-use, the description provides clear context: it is for subdomain enumeration using both passive CT and active brute-force. This is enough for an agent to infer when to choose this tool over simpler lookup tools, but it lacks explicit exclusions or alternative comparisons.

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