run_subfinder

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

The term 'passively' indicates a non-intrusive behavior, which is helpful. However, no annotations are provided, and the description lacks details on output format, dependencies, or potential limitations (e.g., API keys, network access).

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?

Single sentence, no fluff, front-loaded with the key action. Every word earns its place.

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 simple tool with two parameters, the description is minimal. It omits important context like expected output, passive sources used, and whether internet access is required. Given the large number of sibling tools, more context would aid correct selection.

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 already provides descriptions for both parameters ('domain' and 'silent'), achieving 100% coverage. The tool description does not add extra semantic value beyond what the schema offers.

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 the verb 'enumerate', the resource 'subdomains', and the scope 'of a domain', which is specific and distinguishes it from sibling tools like run_nmap or run_gobuster that perform active scanning.

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, such as run_ffuf or run_gobuster. The description does not mention prerequisites, limitations, or context for use.

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