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

Annotations already declare readOnlyHint, destructiveHint, idempotentHint, and openWorldHint. The description adds useful behavioral context such as the return fields (title, ASIN, price, rating, Prime flag, image) and the list of supported marketplaces. No contradictions.

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 relatively concise, conveying purpose, filters, return fields, and marketplaces in one sentence plus a list. It could be more structured (e.g., bullet points) but is efficient and 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 complexity (6 parameters, output schema not provided but description mentions return fields), the description covers purpose, parameters, output, and scope adequately. Missing explicit pagination or error handling, but acceptable for a search tool.

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?

Input schema has 100% coverage with descriptions for all parameters. The description reiterates some parameter info (filter by price range, sort options) and adds the list of marketplaces, which is already partially in the schema description. Minimal added value beyond schema.

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 clearly states the tool searches Amazon products by keyword, lists filters (price range, sort order), and specifies return fields (title, ASIN, price, rating, Prime flag, image). It is distinct from sibling tools like ecommerce.amazon.deals or ecommerce.amazon.product.

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 search with filtering and sorting, but does not explicitly state when to use this tool vs siblings like ecommerce.amazon.deals or ecommerce.amazon.product. The context from sibling names helps, but explicit guidance is missing.

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