theHarvester

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

With no annotations, the description must carry the full burden of behavioral disclosure. It states that harvesting happens from public sources and that output is organized by source, giving some indication of return structure. However, it does not disclose that the tool makes live network requests, may encounter rate limits, or that certain sources require API keys, which an agent would benefit from knowing before invocation.

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 three sentences, each contributing essential information: function and scope, usage context, and output format. It is front-loaded with the most identifying information and contains no filler or repetition.

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 4-parameter OSINT tool with no output schema, the description covers the core requirements: what it does, when to use it, and what it returns. It omits practical caveats like API-key requirements or rate-limiting behavior, but those are partially hinted at in the `limit` parameter schema. Overall it is sufficiently complete for an agent to invoke it correctly in a typical early-reconnaissance workflow.

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 100%, so the baseline is 3. The description adds only a loose contextual link to the `domain` parameter by referencing 'related domains' and 'employee email patterns', but it does not elaborate on `limit`, `source`, or `opts`. This is marginal added meaning above the schema, no penalty is warranted.

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 opens with a specific verb ('harvesting') and lists the resource types (emails, names, subdomains, IPs, URLs), names example sources, and identifies the tool as multi-source OSINT. This clearly distinguishes it from sibling tools like subfinder or amass that focus on subdomains only, and from nmap which scans live hosts.

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 explicitly tells the agent to use it for 'early reconnaissance' and states the intended goals: 'identify employee email patterns, exposed services, and related domains.' It does not explicitly compare against alternatives or give exclusion criteria, but the context is clear enough to route an agent to this tool for passive intelligence gathering.

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