tiktok_search

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

The description mentions 'cursor-based pagination' and 'count clamped to 50', which are behavioral traits not shown in annotations (none provided). However, it omits critical details such as what the tool returns (e.g., video metadata), potential authentication requirements, or any side effects. For a search tool, this is minimally adequate but could be richer.

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 consists of two short sentences that front-load the core purpose. Every word is functional, with no fluff or redundant information. It is highly efficient and easy to parse quickly.

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 simple search tool with three parameters and no output schema, the description covers the basic action and key constraints (pagination, clamping). However, it lacks information about the response format (e.g., what fields are returned for each video) and any rate limits or authentication needs. This missing context reduces completeness for an agent relying solely on the description.

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?

The schema already describes all three parameters (keyword, cursor, count) with 100% coverage. The description's mention of 'cursor-based pagination' adds marginal context, but the clamping detail repeats the schema. With high schema coverage, the description adds little beyond the schema, so a baseline score of 3 is appropriate.

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 'Search TikTok videos' with the verb 'Search' and resource 'TikTok videos'. It specifies the method (by keyword) and pagination approach (cursor-based). This effectively distinguishes it from sibling tools like tiktok_search_hashtag and tiktok_search_user, 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?

The description provides no guidance on when to use this tool versus the many other TikTok search tools (e.g., tiktok_search_hashtag, tiktok_search_user, tiktok_trending). It does not include any 'when-not' or alternative recommendations, leaving an AI agent without context for selection.

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