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

Annotations already establish read-only, idempotent, non-destructive behavior. The description adds useful behavioral context beyond the annotations by specifying that the tool returns structured JSON with organic results, AI overviews, local results, related searches, and more. It does not mention rate limits or failure modes, but these are secondary for a read-only API wrapper.

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 compact: two purposeful sentences plus one short example. The core action and output type are front-loaded, and there is no filler or redundant restatement of the schema.

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 7-parameter tool with no output schema, the description covers the main return shape and gives a reusable invocation example. Minor gaps like pagination behavior or error handling remain, but the schema and annotations cover the rest, leaving the tool adequately specified for an agent to call it correctly.

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 description coverage is 100%, and every parameter has its own meaningful description in the input schema. The description's example demonstrates a real invocation pattern but does not add parameter semantics beyond what the schema already provides, so the baseline of 3 is appropriate.

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 names a specific verb ('Scrape'), a specific resource ('Google Search results'), and the exact API ('ScrapingBee's Google SERP API'). It also lists the structured output types, making the tool's role immediately distinguishable from siblings like scrapingbee_scrape and scrapingbee_ai_extract.

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 scopes the tool to Google Search result scraping via a dedicated SERP API, giving clear context for when it should be used. It provides a concrete invocation example, though it does not explicitly name alternative tools or state when not to use it.

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