dns_intelligence__enumerate_subdomains

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

With no annotations, the description carries the full burden. It usefully discloses the method and that takeovers are confirmed via 'verified fingerprints', but says nothing about network dependence, rate limits, runtime, third-party exposure, or return format — gaps for a multi-source network enumeration tool.

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?

One dense but front-loaded sentence that leads with the primary purpose before the takeover-detection secondary function. No filler, though the tail listing of providers is somewhat verbose.

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 3-param enumeration tool with no output schema and no annotations, the description covers inputs and behavior reasonably. It omits output shape and operational constraints, but the core capability set is conveyed.

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 fully documented in the schema. The description's mention of CT logs and provider CNAMEs loosely maps to the params but adds no syntax or format details 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') and details its two data sources plus takeover detection. However, it does not distinguish itself from the sibling check_takeover, which appears to cover the same takeover capability, leaving some ambiguity about which tool to pick.

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?

There is no explicit when-to-use, when-not-to-use, or alternative guidance. The description never mentions enumerate_dns, lookup_dns, or check_takeover, so an agent must infer routing from the sibling names alone.

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