generate_dorks

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

With no annotations provided, the description must fully disclose behavior. It states 'Passive, public-source collection', indicating non-destructive action, but does not describe return format, side effects, or authentication requirements. The safety profile is partially clear but incomplete.

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 two sentences, front-loading the action and then providing usage guidance. Every sentence adds value without redundancy or excess length.

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 simple tool with two parameters and no output schema, the description covers purpose and target types but omits output format (e.g., list of URLs) and error conditions. This leaves gaps for an agent to understand the full result.

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 description adds meaning to the 'target' parameter by specifying acceptable types (name, email, username, domain), which is not in the schema. However, the 'json_output' parameter is not described beyond its schema description. With 50% schema coverage, the description partially compensates.

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 the verb 'Generate', the resource 'targeted Google dork URLs', and the scope 'for any target (name, email, username, domain)'. It effectively distinguishes from sibling tools that perform searches rather than generation.

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 includes an ethical usage note ('Authorized use only') but lacks explicit guidance on when to use this tool versus alternatives like 'search_dorks_live'. No prerequisites or context for selection are provided.

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