run_sherlock

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

With no annotations provided, the description must convey behavioral traits. It only states the action without disclosing how the search is performed (e.g., asynchronous, rate limits, network requirements), what the output looks like, or whether the tool is read-only or destructive. This lack of transparency hinders an agent's ability to anticipate behavior.

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 9-word sentence that immediately communicates the core action. It is efficiently structured with the verb first. While concise, it sacrifices completeness for brevity, which is acceptable for a simple tool but borderline under-specified.

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 tool has no output schema and no annotations, the description should provide more context about what happens after invocation, such as whether results are returned, how to interpret them, or any network dependencies. The current description is insufficient for an agent to fully understand the tool's complete behavior and output.

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 covers 100% of parameters with a clear description for 'username'. The tool description adds context that the username is searched across social networks and public sites, reinforcing the parameter's purpose. However, it does not add extra constraints or format details beyond what the schema provides, so a baseline score of 3 is appropriate.

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 uses a specific verb 'hunt' and clearly identifies the resource 'username across social networks and public sites'. It effectively distinguishes itself from sibling tools like run_nmap or run_gobuster, which are focused on different tasks such as port scanning or directory enumeration.

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 lacks any guidance on when to use this tool versus alternatives. It does not mention prerequisites, contexts where it is appropriate, or situations where another tool would be preferable. The agent is left to infer usage from the name alone.

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