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

Annotations declare destructiveHint=true, readOnlyHint=false, idempotentHint=false, and openWorldHint=true, but the description adds almost no behavioral context on top of them. It states a Builder task is submitted yet never explains the async nature, what is returned (task id?), that repeated calls are non-idempotent, or why the operation is flagged destructive for what is just data collection.

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?

It is front-loaded with the trigger phrase, but the opening sentence is keyword-stuffed with near-synonymous phrases (Amazon 产品列表 / 商品列表 / 搜索结果列表 / 关键词商品列表) rather than stating the purpose once cleanly. The second sentence is efficient.

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?

For an asynchronous task-submission tool with no output schema, the description should say that a task is created and results are retrieved later (e.g., via scraper_task_status / scraper_task_result). It implies a Builder task but omits the follow-up workflow, leaving an agent unsure what comes back.

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 every parameter (keyword, domain, file_name, page_turning) is already documented in the schema, including defaults and the page-turning semantics. The description adds no meaning beyond that, so the baseline 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 states a specific verb+resource: it submits an Amazon product-list collection Builder task with a fixed collector identifier. However, it does not differentiate itself from the very similar siblings amazon_product, amazon_global_product, and amazon_product_list, so an agent cannot easily tell which one applies.

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?

It gives explicit trigger conditions (product-list / search-result / keyword-product-list requests combined with collect/scrape/crawl/fetch verbs), which is clear usage context. It stops short of naming when-not conditions or an alternative sibling to prefer in edge cases.

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