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

Annotations already declare readOnlyHint=false, destructiveHint=true, openWorldHint=true and idempotentHint=false, so the safety profile is covered structurally. The description adds one genuinely useful behavioral fact beyond that: the call submits a Builder task with a fixed collector id, implying an asynchronous job rather than an inline result. It does not say whether submission is repeatable, what the task does to previously collected data, or what is returned.

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?

Two sentences, but the first is a padded trigger-word list that duplicates the tool name and title without adding selection value, while the second carries all the real information. Front-loading the actual operation would have made this much tighter.

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, and the agent is not told that submission yields a task handle that must be polled or fetched via the scraper_task_status / scraper_task_result siblings. For a task-submission tool in a large scraper family, that missing downstream step is a real gap in an otherwise simple two-parameter 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?

Schema description coverage is 100%, so both parameters (keyword, file_name) are already documented including the default and the non-empty requirement. The description adds only the fixed collector identifier, which is marginal context rather than new parameter semantics, so the baseline 3 applies.

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 second sentence names a concrete verb and resource ('提交 Google 购物信息采集 Builder 任务') and pins the collector id, which tells an agent this submits a scraper task rather than returning product data. However, the opening sentence is essentially a trigger-word expansion of the tool name (Google 购物信息/商品信息/商品数据 + 采集/抓取/爬取), and it never distinguishes this tool from the sibling google_shopping or scraper_serp_products.

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 a trigger condition (user wants Google Shopping data combined with collect/scrape/crawl verbs), but that condition is just a restatement of the tool name's own keywords, not a genuine decision rule. It names no alternatives and no when-not-to-use case, even though google_shopping and bing_shopping sit in the same sibling set.

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