Google search results

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

No annotations are provided, so the description must bear the full burden of behavioral disclosure. It mentions the use of ScrapeUnblocker and the output format, but omits critical details such as rate limits, authentication requirements, cost, or potential side effects (e.g., destructive actions). For a tool that performs an external API call, this lack of transparency is a significant gap.

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 long, front-loading the core action and output format in the first sentence and providing a usage hint in the second. No extraneous words; every sentence adds value.

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 lack of annotations and output schema, the description could be more comprehensive. It covers the basic purpose and usage but does not describe the return structure in detail (e.g., fields in the JSON) or operational constraints. For a tool with three parameters and external dependencies, this is adequate but not complete.

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 100%, and each parameter has a description in the schema. The tool description does not add new meaning beyond the schema; it restates the purpose. According to the guidelines, when coverage is high, a baseline of 3 is appropriate, and the description meets that level.

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 runs a Google search via ScrapeUnblocker and returns organic results as JSON. The phrase 'discover URLs before fetching them' distinguishes it from sibling tools fetch_html and fetch_parsed, which are for fetching specific URLs.

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 explicitly advises to use this tool to discover URLs before fetching, providing clear context for when to invoke it. Although it does not explicitly state when not to use, the sibling tool names imply alternatives, and the guidance is sufficient for an AI agent.

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