theharvester

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

No annotations exist, and the description provides only a high-level purpose without disclosing behavioral traits such as rate limits, data sources, or potential impact on targets. For an OSINT tool, this is insufficient.

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 clause lacking structure or formatting. It is too brief and misses opportunities to add value with minimal additional text.

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 complexity of an OSINT tool and no output schema, the description should explain return values and usage context. It does not, leaving significant gaps for an AI agent.

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?

Only 33% of parameters have schema descriptions (dry_run). The tool description adds no additional meaning for domain or session_id, and the overall description does not clarify parameter semantics beyond what the schema already provides.

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?

Description states 'OSINT gathering from public sources', which is a clear verb and resource. However, it does not differentiate from sibling OSINT tools like amass or dnsrecon, which also perform similar tasks.

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. With many sibling tools performing similar reconnaissance, the description fails to specify scenarios or exclusions.

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