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

With no annotations, the description carries the burden and does well: it discloses latency (<1 second), relative cost (lower credit cost), output shape (clean organic results and top stories), and the one-query-per-call scope limit. It does not mention auth/API-key requirements or rate limits, so it falls short of a full behavioral profile.

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?

Front-loads the primary purpose and cost/latency benefit, then the routing rule, then the scope constraint with the CLI escape hatch. Every sentence earns its place with no redundancy.

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 search tool with a full schema and an output schema already covering return values, the description supplies what structured fields cannot: primary-vs-alternative routing, cost/latency expectations, and the single-query scope limit. Nothing an agent needs to call it correctly is missing.

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%, so all five parameters (search, page, language, country_code, tag) are already documented in the schema. The description adds no syntax or format detail beyond what the schema provides, so the baseline 3 is correct.

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?

States a specific verb+resource ('Search the web using ScrapingBee's Fast Search API') and explicitly positions itself as the PRIMARY general web-search tool. It names the sibling it is not (get_google_search_results) and the conditions that select it, so an agent can pick it apart from siblings without reading either schema.

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?

Gives explicit when-to-use ('USE THIS TOOL FIRST for any general web search') and a clear when-not with the alternative named ('Only fall back to get_google_search_results if you need ... news, maps, Google Lens, shopping, image search, or Google AI mode'). Routing guidance is unambiguous.

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