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

With no annotations provided, the description carries the full burden. It discloses pagination behavior ('each page returns up to 50 ranked items'), the typical top-100 coverage, and the fields included in each item. It does not mention authentication, rate limits, or error behavior, but for a read-only rankings tool the disclosed behavior is substantial.

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 tight sentences deliver the core action, the supported ranking types, the return fields, and pagination constraints. There is no fluff or repetition of obvious information.

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?

Given no output schema or annotations, the description does a good job of explaining what the response contains and how pagination works. It could be more complete by noting valid country-code values or potential limitations, but the essential information for selecting and calling the tool is present.

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 the baseline is 3. The description adds meaningful context beyond the schema by explaining page size, top-100 coverage, and what each returned item contains. It reinforces the enum values and category slug concept, though it does not add much detail for the country parameter.

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 starts with a specific verb and resource: 'Get Amazon best-seller rankings for a category.' It enumerates the supported ranking types and clarifies that the result is a ranked list, which clearly distinguishes it from sibling product-search and product-detail tools like search_amazon_products and amazon_product_details.

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 makes the tool's purpose immediately evident: use when you need category best-seller rankings rather than product details or free-form product searches. It does not explicitly name alternatives or state when not to use it, but the context is clear enough that an agent can route appropriately.

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