search_dorks_live

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

With no annotations, description discloses it is a paid API call, requires specific secrets, is passive and read-only, and returns live results. It doesn't detail error handling or rate limits, but for a search tool this is sufficient context.

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?

Three sentences that front-load the core purpose, then add essential details (billing, setup, legal). No extraneous words; every sentence earns its place.

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 2-parameter tool with no output schema, the description covers what the tool does, data source, result structure, default behavior, prerequisites, and legal context. Complete enough for an agent to use confidently.

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 50% (only json_output has description). The description adds context for 'target' as the search target but doesn't specify format. It does not elaborate on json_output beyond what schema already provides; baseline 3 is appropriate given partial coverage.

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 it executes Google dork queries via Bright Data SERP API and returns structured results with title, URL, and snippet. It distinguishes itself from sibling tools like search_email or search_domain by explicitly focusing on dork queries.

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?

Describes when to use (for dork queries), mentions default limit of 5 dorks, billing implications, required env vars, and authorized use. However, it does not explicitly state when not to use this tool instead of alternatives like search_domain or search_crt.

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