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. The description adds one useful behavioral fact: that this is an asynchronous 'Builder' task submission rather than a direct fetch. It does not disclose what the task returns, whether a task ID must be polled via scraper_task_status, or any rate/credit implications, so the value added is modest.

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 first sentence is heavy keyword stuffing, repeating near-identical phrases ('TikTok 帖子信息, Tiktok 帖子信息, TikTok 视频帖子...'), which crowds out the actual purpose. The real functional statement ('submits a Builder task...') is buried in the second sentence rather than 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?

With no output schema and three parameters, the description should clarify the task lifecycle, but it stops at 'submit a Builder task'. An agent is left unsure whether the call returns data directly or only a task handle requiring a follow-up status/result query, which is a meaningful gap for an async scraping 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 all three parameters (url, file_name, num_of_posts) are already documented with defaults and semantics. The description only echoes the collector identifier and adds no format or constraint detail beyond the schema, so 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 and resource: it submits a TikTok posts collection 'Builder' task and pins the collector identifier as tiktok_posts_by-listurl. This clearly tells an agent what the tool does. However, it never distinguishes itself from closely related siblings like tiktok_profiles or tiktok_comment, so sibling differentiation is absent.

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 gives trigger conditions via keyword combinations ('collect/scrape/crawl/fetch' + 'TikTok posts'), which implies when to invoke. But it offers no when-not-to-use guidance and names no alternative tool (e.g., tiktok_profiles for profile data), leaving the agent to infer boundaries against a large sibling set.

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