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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds genuinely new behavior: result ordering ('best match first — priced and recently observed rows lead'), a cache-miss fallback that hits Amazon live with a 10-20 second latency penalty, and the one-barcode-per-call limit. It stops short of describing empty/no-match behavior or rate limits, so not a full 5.

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?

Front-loaded with the purpose, then trigger, then return shape, then the latency caveat and the routing note. The example phrasings are somewhat redundant with the trigger sentence, but the whole block is tight and every remaining sentence carries 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?

No output schema exists, and the description covers the return fields (ASIN, brand, title, price, rating, image) and ordering, plus the live-search latency and the one-per-call constraint. An agent has everything needed to call it correctly and set expectations about timing.

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% — both barcode and marketplace_id carry full descriptions with the marketplace enum spelled out. The description restates the accepted barcode formats but adds nothing about the marketplace_id parameter (e.g. that matching is marketplace-scoped), so it neither compensates nor regresses beyond the schema baseline.

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 ('Look up products by retail barcode') plus the supported symbologies (UPC-12, EAN-13, GTIN-14). It distinguishes itself from siblings by naming bulk_product_lookup for list input, so an agent can separate it from search_products without opening either schema.

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?

Explicit when-to-use trigger ('when the user gives a numeric product barcode from a shelf tag, invoice, price list, catalog') with concrete user-phrasing examples, plus the explicit exclusion 'One barcode per call; for a list use bulk_product_lookup.' Both the use case and the alternative are named.

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