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

Annotations declare destructiveHint=true, openWorldHint=true, idempotentHint=false, readOnlyHint=false – a mutable, non-idempotent, open-world write. The description notes it submits a Builder task and the fixed collector ID, adding task-creation context, but does not disclose side effects, async/non-idempotent duplication risk, or output/result retrieval path (scraper_task_status/result).

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 front-loads a keyword-stuffed trigger list (TikTok 商店信息, Tiktok 商店信息, TikTok Shop 信息, TikTok 店铺信息 plus 采集/抓取/爬取/获取/提取) which is repetitive and adds little decision value. The actual purpose is buried in the trailing sentence, wasting the prime position.

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 a task-submission tool with no output schema, the description covers the collector identity and trigger context, and the schema covers both parameters. However, it omits how to retrieve task results, failure behavior, and any auth/rate constraints, leaving gaps for correct invocation of a destructive, non-idempotent operation.

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 url and file_name are already documented in the schema including the default '{{TasksID}}'. The description adds no syntax, format, or behavioral detail beyond the schema, so 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 description states a specific action: submitting a TikTok shop info collection Builder task with a fixed collector identifier 'tiktok_shop_by-url'. It distinguishes itself from siblings like tiktok_posts/tiktok_profiles by naming the tiktok_shop collector, though the trigger-phrase preamble is keyword spam rather than a crisp purpose statement.

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?

Usage is implied via trigger-phrase combinations (user needs TikTok shop info plus a scrape/fetch verb), which gives some sense of when to fire. But there is no explicit when-not-to-use or comparison to sibling tools like tiktok_posts or scraper_task_* alternatives.

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