Google Search (SERP) API

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

With no annotations provided, the description carries the full burden. It discloses that results are returned as structured JSON and mentions result types, which is useful, but it does not cover critical behavioral aspects such as API key requirements, rate limits, pagination behavior, or latencies. The 'real-time' and 'scrape' wording hints at live fetching but lacks depth.

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, concise sentence that front-loads the core function and provides a representative list of output components. Every word earns its place, with no redundancy or filler.

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's complexity (12 params, no output schema, no annotations), the description is adequate but not complete. It communicates the return format and general content, and the schema fills parameter gaps, but it misses usage context (e.g., when to use vs. siblings) and behavioral details. It does not fully compensate for the absent output schema and annotations.

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 has 100% description coverage, so the schema already documents all 12 parameters with clear descriptions. The tool description adds no additional parameter-level meaning or examples, so it meets the baseline but does not elevate it.

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's function with a specific verb ('Scrape') and resource ('real-time Google Search results'), and explicitly lists the output types (organic results, ads, knowledge graph, people-also-ask). This distinguishes it from sibling tools like google_news or google_images, which target specific verticals.

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 this is the general-purpose Google SERP tool, covering a broad range of search result types, which provides clear context for when to use it. However, it does not explicitly contrast with alternatives or state when not to use it, so it stops short of full exclusions or alternative guidance.

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