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

Beyond the readOnly/openWorld annotations, the description discloses three genuinely useful behaviors: results may contain duplicates (a TikTok-side issue outside the caller's control), pagination via cursor, and that completed lookups consume credits with repeated requests potentially repurchasing the same data. Those additions are valuable, but the credit disclosure is self-contradictory ('at least 10 Nexscope credits' versus '1 credit per request'), which weakens trust in the cost signal.

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 text reads as concatenated supplier and pricing boilerplate: the duplicate-results caveat is stated four times, including a conversational apology, followed by a restatement of the title and two different credit figures. Useful facts (return shape, duplicates, cost) are buried in repetition rather than front-loaded.

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 does the work of describing the return payload (search_item_list of aweme_info with aweme_id, desc, statistics, video, author), which is exactly what an agent needs. It also flags duplicates and credit cost; only the pricing inconsistency and absent return-size/pagination limits keep it from being fully 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 description coverage is 100%, including the non-obvious region-proxy caveat and the sort_by/date_posted enums, so the schema already carries parameter meaning. The description only reinforces cursor-based pagination; it adds nothing about how query, region, or the sort/filter params interact. 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?

The opening sentence gives a specific verb and resource ('Searches for TikTok videos by keyword or phrase') and scopes it as 'the general video search across all of TikTok', which implicitly separates it from hashtag, user, and top-search siblings. It stops short of naming an actual alternative tool, so an agent must infer the routing.

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?

Usage is implied by 'general video search' rather than stated: there is no explicit when-to-use/when-not, no pointer to social_tiktok_search_top, social_tiktok_search_hashtag, or social_tiktok_video_search as the alternative for those cases. Pagination guidance ('Paginate with cursor') is the only operational instruction.

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