Amazon Bestsellers

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

Annotations already declare readOnlyHint=true, openWorldHint=true, destructiveHint=false, so the safety profile is covered. The description adds useful context beyond that — the request is proxied through the Decodo Web Scraping API target `amazon_bestsellers` and results come back parsed as JSON — but says nothing about pagination limits, failure modes, or latency for what is an external scrape.

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 sentences plus a docs link: purpose first, then usage intent, then reference material. Nothing is repeated from the schema and nothing is wasted.

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 three-parameter read-only scrape with full schema coverage and no output schema, the description covers purpose, mechanism, and return type (parsed JSON), plus a docs link for deeper detail. Minor gaps: no mention of domain defaults or pagination depth limits.

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 coverage is 100%, so query, domain, and pageFrom are each documented in the schema; baseline is therefore 3. The description adds only that the request is 'for a category', which loosely maps to `query`, and gives no extra detail on domain defaults or pageFrom behavior.

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 ('Fetch the Amazon Best Sellers list for a category') and notes the parsed-JSON result, which clearly separates it from siblings like amazon_search or amazon_product. It stops short of explicitly naming an alternative tool, but the resource specificity makes selection unambiguous.

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?

'Use it to see the top-selling products in a category' gives an implied usage context, but there is no explicit when-not guidance and no named alternative (e.g., amazon_product for a single item, amazon_sellers for seller data). The agent must infer the boundaries from the tool name alone.

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