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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, openWorld), so the description's value-add is elsewhere: it states the return ordering, the fields returned, and a billing model (¥0.1 per call, charged only on success, auto-refund on failure or empty results). That cost/refund disclosure materially changes how an agent should batch or retry. Pagination and rate-limit behavior remain unstated.

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?

Four short sentences with a clear front-load: what it returns, its ordering and fields, when to use it, then cost. Every sentence carries distinct information and nothing is repeated from the schema or annotations.

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 read-only list tool with no output schema, it adequately describes the result shape (reverse-chronological list, content IDs, engagement data) and discloses the billing consequence of empty results. The two remaining gaps are pagination/volume limits and how to source the sec_uid.

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 coverage is nominally 100%, but the sec_uid entry is a tautology ('secUid'), so the schema adds no real meaning, and the description only implies that a user identifier is required without explaining where to obtain a secUid. Baseline 3 applies given the declared coverage, but the description does nothing to compensate for the vacuous parameter doc.

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 opens with a specific verb and resource (获取TikTok用户视频列表) and adds scope detail that the name alone does not convey: per-account, reverse-chronological, content IDs plus basic engagement metrics. That clearly separates it from tiktok_post_detail or tiktok_keyword_search, though no sibling is named explicitly.

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 concrete trigger scenarios (monitoring account posting frequency, content strategy analysis, bulk-retrieving a creator's content IDs), which is more than most list tools offer. It stops short of exclusions or named alternatives, so the agent must still infer that per-post data should go to tiktok_post_detail and profile data to tiktok_user_info.

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