best_sellers

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

No annotations are provided, so the description carries the behavioral burden. It discloses the scope (Amazon Best Sellers listings only), the data points returned, and the multi-country/domain behavior. It does not reveal rate limits, authentication needs, or response pagination limits, but the rich parameter docs compensate partially.

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, front-loaded with the core purpose. The markdown bold formatting for the list types aids scannability. The category example and URL are useful but add length; still every sentence earns its place, and the bulk of detail is correctly delegated to the schema.

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 6-parameter tool with no output schema, the description reasonably covers the main purpose, list-type variants, and category-path flexibility. It doesn't describe return shape, but schema covers parameters comprehensively. Slightly lacking on what the data response contains structurally, though the description does name key data points (prices, ratings, rank).

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 this dimension sits at baseline 3. The description adds value by explaining that the category parameter supports both top-level categories and subcategory paths (with URL example), extending beyond bare schema text. However, most semantics are already well-documented in the schema parameters themselves.

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?

Clear verb+resource (Get Amazon Best Sellers) with explicit details on what data points are returned (prices, ratings, rank, etc.). The description also distinguishes from siblings by noting it supports all Best Seller list types via the type parameter, differentiating from product_search, deals, and product_category_list.

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 explains the type parameter covers different list variants (Best Sellers, New Releases, Movers & Shakers, etc.), giving clear context for when to use each variation. It doesn't explicitly name alternative tools to avoid, but the category-path support (category/229535) provides practical usage guidance beyond bare schema.

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