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

With no annotations provided, the description carries the full transparency burden. It discloses the return fields (ASIN, title, price, rating, Prime status, etc.), pagination behavior (~16 results per page), and available filters, which gives an agent a solid behavioral model of a read-only search operation. It does not go into rate limits or data freshness, but the disclosed behavior is substantially more than minimal.

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 description is three tightly written sentences: what it does, what it returns, and what filters/pagination to expect. Every sentence adds value and the core action is front-loaded.

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 the tool's complexity (14 parameters, no output schema), the description covers the key contextual gaps: return fields, marketplace scope, filters, and page size. It does not enumerate every parameter, but the schema already handles that. A short mention that queries can also be ASINs would have made it fully complete, but the current level is strong.

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 schema fully documents all 14 parameters. The description provides a useful high-level summary of filter categories and page size, but it does not add meaning beyond what the schema already states, so the baseline of 3 is appropriate.

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 opens with a specific verb and resource ('Search Amazon products by keyword') and adds a concrete scope ('across 24 marketplaces'). This clearly distinguishes it from sibling tools like amazon_product_details or amazon_seller_products, which target different lookup modes.

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 implies usage for keyword-based Amazon product discovery and lists filter capabilities, but it never explicitly states when to prefer this tool over alternatives like amazon_best_sellers or amazon_seller_products. There are no exclusions or when-not-to-use conditions.

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