search_tiktok_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 the output structure (JSON with specific fields) and pagination behavior (using data.cursor and data.has_more), which are important behavioral traits. It does not cover error conditions or rate limits, but the pagination detail adds significant value beyond the schema.

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 extremely concise at two sentences, front-loading the main action and result format. Every sentence serves a purpose: stating the action and output, and providing pagination instructions. No wasted words.

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, the description compensates by listing output fields and explaining pagination. The schema covers parameters well. It lacks error handling or fallback behavior, but for a search tool with siblings covering other platforms and TikTok-specific queries, the description is reasonably complete.

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% with descriptions for all three parameters. The description adds value by explaining how to use the cursor parameter for pagination, but does not add meaning for keyword or count beyond what the schema provides. Baseline 3 is appropriate given high schema coverage and the additional cursor context.

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 clearly states the verb 'Search' and the resource 'TikTok users', specifies the output format (JSON) and key fields included in each result. This distinguishes it from sibling tools like search_tiktok_videos which search videos, making the purpose unambiguous.

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 provides clear context for using the tool (searching users by keyword) and includes pagination instructions, but does not explicitly advise when not to use it or mention alternative tools. However, sibling tool names like get_tiktok_profile and search_tiktok_videos make the differentiation fairly obvious.

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