run_amazon_product_search

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

With no annotations, the description carries the full burden. It discloses useful behavioral context: pagination, returned fields, and a cost model of '1 point per returned record.' It does not mention read-only safety, permissions, rate limits, or failure behavior, so it is only partially transparent.

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 definition is a single, front-loaded sentence with no filler. Every phrase contributes: action, resource, extracted fields, pagination, and cost.

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?

There is no output schema or annotation coverage, but the description names the key returned fields and mentions pagination and cost. Combined with the fully described input schema, this is sufficient for an agent to call the tool correctly, though it could say more about domain handling or large result sets.

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 query, domain, max_items, and start_page are already documented in the schema. The description adds only indirect context through 'paginated results' and the per-record cost, which loosely relates to max_items and start_page but does not explain them.

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 names a specific verb and resource: 'Search Amazon and extract product listings.' It also identifies the returned fields (title, URL, price, rating) and pagination scope, so the agent can distinguish this from non-search Amazon tools. It does not explicitly name sibling alternatives such as run_amazon_product or run_amazon_product_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 search framing implies when to use the tool, and the mention of paginated results gives some operational context. However, it does not state when to prefer this over run_amazon_product, run_amazon_product_offers, or other marketplace search tools, nor does it give exclusions or prerequisites.

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