tiktok_search_users

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

No annotations are provided, so the description carries the full burden. It discloses pagination behavior ('cursor 翻页游标第一页为 0、每页 +10；rid 为上一页数据返回的 rid，翻页时传入') and return fields ('返回含 cursor/hasMore/userList'). However, it does not specify any destructive/read-only nature, authentication needs, or rate limits.

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 concise (two sentences) and front-loaded with the main purpose. It packs pagination logic and return fields efficiently. Minor punctuation issues but still clear.

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 3 parameters and an output schema exists, the description covers pagination behavior adequately. However, without annotations, it could still benefit from additional behavioral context (e.g., whether the tool is read-only, any prerequisites). The output schema likely documents return values, so the description's mention of return fields is somewhat redundant but helpful for quick understanding.

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 0%, so the description must compensate. It explains keyword (required), cursor (starts at 0, increments by 10 per page), and rid (needs to be passed from previous page). However, it does not clarify default values or acceptable formats beyond the schema's type definitions.

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 '搜索 TikTok 账号' (search TikTok accounts), using a specific verb and resource. However, it does not differentiate from sibling tools like 'douyin_search_users' or 'xiaohongshu_search_users', as they all search users on different platforms. The platform name in the tool name and description provides some differentiation.

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 mentions that 'keyword' is required and explains the cursor and rid parameters for pagination, implying how to use the tool for paginated searches. However, it does not provide guidance on when to use this tool versus alternatives (e.g., for TikTok-specific user searches) or any exclusions.

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