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

No annotations are provided, so the description carries the full behavioral burden. It usefully discloses scoping (one query per call) and where output lands (conversation vs disk via CLI), but says nothing about authentication/API key needs, credit consumption or rate limits for the ScrapingBee backend, or error behavior—notable gaps for a paid scraping call.

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?

Two short sentences, both earning their place: the first states purpose, the second states scope and the batching/disk alternative with a concrete command example. It is front-loaded and free of repetition.

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?

With an output schema present, return values need not be explained, and the schema fully documents parameters. But with zero annotation coverage on a network-scraping tool with 11 parameters, the description leaves authentication, cost/credit implications, and failure modes unaddressed, which is the main completeness gap.

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%, with all 11 parameters documented in the schema itself (including the ASIN requirement, domain/country conflict rule, and localization options). The description adds no parameter-level meaning beyond the generic word 'query', so the baseline 3 applies.

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 states a specific verb and resource ('Scrape Amazon product details using ScrapingBee'), which is clearly distinct from the generic page/search siblings. However, it never names the closest siblings (get_amazon_search_results, get_amazon_pricing, get_walmart_product_details), so the agent must infer the boundary rather than being told it.

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?

It explicitly states the usage constraint ('one query per call') and names the alternative (the ScrapingBee CLI) with the conditions that select it: many queries in one pass, or writing to disk instead of the conversation. It does not, however, explain when to prefer this over sibling tools like get_amazon_search_results or get_amazon_pricing.

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