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

Beyond the read-only and open-world annotations, the description discloses scraping behavior, response contents, cursor-based pagination, credit charges, and the possibility that repeated requests purchase data again. These are useful operational details, although the statements 'at least 10 Nexscope credits' and '1 credit per request' are not clearly reconciled.

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 purpose, return shape, and pagination guidance are front-loaded and easy to find. The ending degenerates into redundant copied fragments such as 'TikTok Search Users API View Pricing' and repeats pricing information in a potentially confusing way.

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 three-parameter search tool with no output schema, the description supplies the important purpose, representative response fields, pagination mechanism, and billing considerations. It remains short of excellent because associated 'items' are unexplained, trim behavior is unclear, and the pricing details are ambiguous.

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 the schema already documents query, cursor, and trim. The description adds modest context by describing the query as a keyword or name and demonstrating cursor-based pagination, but it does not clarify what a trimmed response omits.

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 clearly states the action, resource, and matching criteria: searching TikTok users by keyword or name to find creators or accounts. It does not distinguish this tool from siblings such as social_tiktok_search_keyword, social_tiktok_search_top, or nexscope_tiktok_creator_search.

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 phrase 'useful for finding creators or accounts matching a query' gives a clear use case, and the pagination instruction explains how to continue a search. However, there is no guidance on when to prefer a profile lookup or another TikTok search tool.

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