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

No annotations are provided, so the description carries the full burden. It does disclose a real behavioral trait in '1 point per returned record', which tells the agent about cost scaling with max_items, but it omits auth requirements, pagination behavior, and any failure modes.

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 short sentences, zero filler, with the resource and return fields front-loaded before the cost caveat. Every clause earns its place.

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 no output schema, listing the returned fields is valuable and it adds the point-cost model. It falls short on pagination semantics (how start_page and max_items interact across the 250-item cap) and on how to obtain a seller ID, but nothing critical for a simple read tool is missing.

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 domain, seller, max_items, and start_page are already documented with defaults and bounds. The description adds no parameter-level detail; the cost note only loosely connects to max_items. Baseline 3 applies.

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?

States a specific verb and resource ('List products sold by an Amazon seller's storefront') and enumerates the returned fields (title, URL, price, rating, image). This clearly separates it from run_amazon_product (single product) and run_amazon_seller (seller profile) among the siblings.

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?

Usage is only implied by the phrase 'sold by an Amazon seller's storefront' – the agent can infer it takes a seller ID and returns that seller's catalog. No explicit when-to-use, when-not-to-use, or named alternatives (e.g. run_amazon_seller, run_amazon_product_search) are given.

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