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

Annotations already declare the operation read-only, idempotent, and non-destructive, so the safety profile is covered. The description adds that results are 'structured' and lists returned fields, which is useful but doesn't address pagination, result limits, or API-key behavior; acceptable but minimal.

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 one focused sentence followed by a code example. It front-loads the purpose, and the example earns its place by demonstrating required parameters and a realistic call, with very little wasted text.

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?

The tool is simple, the schema covers all parameters, and annotations cover safety, so the description is mostly sufficient. However, there is no output schema and the description does not specify the result shape, array vs. object, pagination, or limits, leaving some ambiguity for an agent consuming the results.

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 the schema already documents all four parameters. The example call adds a concrete invocation pattern but no new semantic meaning beyond the schema; this meets the baseline without needing extra compensation.

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 says 'Search Amazon' and lists the exact structured outputs (titles, ASINs, prices, ratings, thumbnails), so the tool's core purpose is unmistakable. It doesn't explicitly contrast with sibling tool scraperapi_amazon_product, but name and output list make the distinction largely inferable.

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?

No guidance is given on when to use this tool versus alternatives like scraperapi_amazon_product, scraperapi_google_search, or scraperapi_scrape. The only hint is the example call and the word 'Amazon', so an agent has to infer usage context on its own.

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