Amazon Search API

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It mentions 'scrape' which suggests an unofficial/hard-scrape nature, but it does not disclose specifics like rate limits, proxy usage (despite the premium param), pagination behavior, or success rates. The description provides minimal transparency beyond the action itself.

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 sentence, front-loaded with the key action and resource. It is concise and free of filler, making it easy to parse quickly. It earns a perfect score for conciseness and structure.

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 7 parameters, no output schema, and no annotations, the description is far from complete. It lacks any information about return format, result structure, error handling, or behavioral nuances. For a scraping tool with low-level parameters, this is critically insufficient.

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 covers 100% of parameters with descriptions, so the baseline is 3. The description only mentions 'query' implicitly via 'for a query', adding no additional meaning beyond what the schema already provides. It does not explain how parameters like domain, country, or premium interact.

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 scrapes Amazon search-result listings for a query. The verb 'scrape' and resource 'Amazon search-result listings' are specific, and the phrase 'search-result listings' helps distinguish it from sibling tools like amazon_product, amazon_reviews, and amazon_offers.

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 gives no guidance on when to use this tool versus alternatives (e.g., google_search, amazon_product). It does not mention any context, prerequisites, or exclusions. The only implied usage is 'for a query', but there is no explicit comparative guidance.

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