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

With no annotations provided, the description carries the behavioral disclosure burden. It reveals the core behavior: brute-force resolution of a common-subdomain wordlist against a target. It does not mention potential side effects like volume of DNS queries, wildcard handling, rate limits, or whether only live subdomains are returned, but the basic operation is clear.

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 a single compact sentence with no filler. It front-loads the tool's identity and immediately states the operation and scope, earning every word.

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?

This is a simple one-parameter tool with an output schema, so the description does not need to explain return values. However, it leaves the q parameter under-specified and provides no routing guidance among closely related subdomain tools, making it minimally adequate but not 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?

The input schema has one opaque parameter 'q' with 0% schema coverage, so the description must compensate. The phrase 'per-target' weakly implies q is the target domain, but the description never explicitly states what q represents, what format is expected, or whether it accepts domains, hosts, or URLs.

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 states a specific action ('Resolve') and resource ('common-subdomain wordlist') applied per target, so an agent can tell this is a subdomain enumeration tool. It does not explicitly name sibling alternatives, but 'Subdomain Brute' and 'per-target' make the core function clear.

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 phrase 'per-target' implies the tool should be invoked with a single target domain and that it uses a fixed common-subdomain wordlist. However, there is no explicit guidance about when to choose this over similar siblings such as subdomains, dnsrecon, or hosthunt, and no exclusions are stated.

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