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

Annotations already cover the read-only and open-world nature of the operation, so the safety profile is clear. The description adds only that pagination via page_token is supported, which is also documented in the schema; it offers no additional context such as rate limits, data freshness, or result completeness. No contradiction with annotations.

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 is a single, front-loaded sentence that names the action, the resource, the input key, and the pagination behavior with no filler or redundant content.

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 a rich input schema, an output schema, and annotations covering read-only/open-world behavior, the core invocation context is sufficiently complete. The only meaningful gap is the absence of explicit routing to tiktok_get_user_posts_by_tiktok_id when a TikTok ID rather than a profile URL is available, but this is a minor omission for a simple list endpoint.

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 100%: both profile_url and page_token are already documented, with detailed handling rules for the opaque token. The description restates page_token pagination but adds no semantic meaning beyond what the schema provides.

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 uses a specific verb phrase ('获取作品列表' / get posts list) and identifies both the resource (TikTok user's posts) and the access path (profile URL). This clearly distinguishes it from sibling tools such as tiktok_get_user_posts_by_tiktok_id and tiktok_get_user_info_by_profile_url.

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 implies the main usage: call this tool when you have a TikTok profile URL and want that user's posts. However, it does not explicitly state when to prefer this over tiktok_get_user_posts_by_tiktok_id or other siblings, and it gives no exclusions or alternative routing guidance.

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