search_dorks_live

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

Since no annotations are provided, the description carries the full burden. It discloses that up to 5 dorks run by default, each incurring a billable API call, and requires specific env vars. It also notes passive, public-source collection and authorized use. However, it lacks details on error handling, rate limits, or pagination.

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, well-structured paragraph that front-loads the main purpose. It includes prerequisites and legal caveats without unnecessary verbosity, though a slight reorganization could improve scanability.

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 no output schema and only two parameters, the description covers the main behavioral aspects but lacks specifics on output structure, error responses, and default dork list. It is adequate for a simple tool but incomplete for richer understanding.

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 by stating the tool returns title, URL, and snippet, but it does not clarify the 'target' parameter (whether it is a dork query or target domain). With only 50% schema description coverage, the description partially compensates but leaves ambiguity.

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 tool executes Google dork queries for a target via the Bright Data SERP API, returning structured results. It is specific and distinguishes from sibling search tools that focus on different data sources.

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 implies usage for dork queries and mentions prerequisites and authorization, but does not explicitly compare with alternatives or state when not to use it. Usage context is implied but not fully explicit.

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