dns_intelligence__enumerate_subdomains

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

With no annotations present, the description carries the full burden, and it does real work: it names the data sources (crt.sh, Cert Spotter), discloses that only the domain name is sent to them, and notes that provider fingerprints are verified rather than guessed. Gaps remain around rate limits, runtime, and the fact that httpProbe issues live HTTP requests to third-party hosts, so it is not fully complete.

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?

A single front-loaded sentence puts the primary action first and appends the takeover-detection scope. It is dense but every clause adds information; the provider list is mildly long but concrete. Minor run-on structure keeps it from a 5.

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?

For a three-parameter tool with no output schema and no annotations, the description conveys enough: what is enumerated, from which sources, and what kind of finding (dangling provider CNAME) results. It stops short of describing result shape or handling of partial failures, which is the remaining gap.

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 all three parameters are already documented in the schema. The description restates the same concepts (CT logs, provider fingerprint probing) at a slightly higher level without adding syntax, defaults, or edge-case behavior beyond what the schema provides. Baseline 3 applies.

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?

States a specific verb and resource: find subdomains from Certificate Transparency logs and a wordlist, plus detect subdomain takeovers via dangling CNAMEs to named providers. That is far more specific than a bare 'enumerate' label. It doesn't explicitly contrast with the sibling tools dns_intelligence__check_takeover or dns_intelligence__enumerate_dns, which overlap meaningfully, so it falls short of a 5.

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 implies when it is appropriate (broad enumeration plus takeover detection in one pass), but never says when to prefer the narrower check_takeover or enumerate_dns siblings, nor does it state prerequisites like needing authorization to probe third-party hosts. Usage is inferable but not explicit.

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