tools_subfinder

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

With no annotations provided, the description must disclose behavioral traits but only states 'Execute Subfinder' with no details on potential side effects, resource usage, or required network access. It does not mention that Subfinder is a passive tool or any other characteristics.

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 concise with two sentences followed by a simple args listing. It is front-loaded and to the point, though the args formatting could be more formal. No wasted sentences.

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?

Given the existence of an output schema (not shown) and the tool's relative simplicity, the description is incomplete. It lacks context about execution time, required network access, or the passive nature of Subfinder. The output schema may cover return values, but behavioral context is missing.

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 0% description coverage, so the description's brief explanation of 'target: Target domain' and 'additional_args: Extra subfinder arguments' adds essential meaning. While brief, it clarifies the purpose of each parameter where the schema is silent.

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 'Execute Subfinder for subdomain enumeration.' This provides a specific verb and resource, making the tool's purpose evident. However, it does not differentiate from sibling subdomain enumeration tools like tools_amass or tools_subzy.

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 offers no guidance on when to use Subfinder over other subdomain enumeration tools or what prerequisites exist. It simply states what the tool does, without any context about alternatives or appropriate scenarios.

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