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

Adds substantial behavior beyond the readOnlyHint/openWorldHint annotations: it discloses the data quirk that following_count and posted_content_count are currently null, and states the precise pagination rule (continue only when next_page_token is non-empty). These are non-obvious traits an agent must know.

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?

Purpose and pagination rule are front-loaded and efficient, but the output-chaining clause is stated twice for tiktok_id and profile_url with near-identical wording, adding mild redundancy to an otherwise dense description.

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?

Given a 2-param read-only search with an output schema, the description is complete: it covers query scope, pagination continuation, known null fields, and how returned identifiers feed sibling tools. Nothing needed to call it correctly is missing.

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 keyword and page_token are already fully documented in the schema, including the non-empty pattern and the page_token opaque-token rules. The description reinforces the pagination-continuation rule but adds little parameter meaning 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?

States a specific verb and resource (搜索 TikTok 用户) and the query types it accepts (用户名、昵称、品牌名). It is clearly distinguishable from siblings like tiktok_search_posts and tiktok_search_suggestions, which target different resources.

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?

Gives explicit when-to-use and, crucially, when-NOT-to-use: if the exact user identifier is already known and only follow-up data is needed, skip the search and call the corresponding entry directly. It also names which downstream tools accept the returned tiktok_id/profile_url, routing the agent precisely.

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