Run passive Subfinder discovery

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

Annotations already declare readOnlyHint=true, openWorldHint=true, idempotentHint=true, and destructiveHint=false, covering the safety profile. The description adds two useful traits beyond that: the binary must be 'explicitly enabled' (an environment/config precondition) and results are filtered to 'in-scope subdomains' (a post-processing behavior). It does not mention rate limits, source coverage, or timeout behavior, so a 3 is appropriate.

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 that names the action, the tool, and the scope with no filler. It is efficient, though the trailing scope-filter clause is doing double duty that could be unpacked without bloat.

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?

An output schema exists, so return values needn't be described, and annotations cover safety. However, for a crowded discovery toolset the description omits any guidance on when this run is preferred over the many sibling subdomain/DNS enumeration tools, leaving a real gap for correct tool 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?

Schema coverage is 0% and there is one required parameter, so the description carries the burden. 'One authorized domain' hints that the value is a single in-scope domain rather than a list, but it gives no format, normalization, or edge-case detail (subdomain vs apex, wildcard handling) beyond what the bare schema string type implies.

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 ('Run') plus the resource (the Subfinder binary) and scopes it to one domain, so an agent knows this is a targeted passive-subdomain discovery run. It names Subfinder specifically, which gives mild differentiation from the generic 'subdomain_enumeration' sibling, but it never contrasts itself against near-identical tools like amass_passive_discovery or assetfinder_discovery.

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 a constraint ('one authorized domain') but no explicit when-to-use or when-not-to-use guidance. In a sibling set containing subdomain_enumeration, amass_passive_discovery, assetfinder_discovery, and dns_enumeration, an agent is left to guess which discovery tool is appropriate; the description offers no routing signal.

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