tiktok_search: GET /

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

No annotations are provided, so the description carries the behavioral transparency burden. It fully explains what the search returns, mentions pagination via nextPageToken, and even notes that authors and users carry links to profile and posts endpoints. It does not mention rate limits or auth, but it clearly establishes a read-oriented search behavior and pagination model.

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 organized and front-loaded with the main purpose: Search TikTok. The following sentences add necessary details about return fields, linked data, pagination, and intended use cases without excessive filler. It could be slightly tighter, but every sentence earns its place.

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 three-parameter tool with no output schema, the description covers the result shape, pagination behavior, and use cases well. It gives enough information for an agent to invoke the tool with a keyword and interpret the response, though it does not cover edge cases or error conditions.

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 input schema already documents all three parameters with 100% coverage. The description adds some context around pagination and result types, but it does not significantly enrich parameter meaning beyond what the schema already provides. Therefore, the 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 description clearly states that this tool searches TikTok by keyword and returns either videos or users, enumerating the key result fields for both. This is a specific verb+resource description and is easily distinguished from the sibling profile, posts, and comments tools.

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 gives explicit context for when to use it: content discovery, trend research, influencer discovery, or building datasets from a keyword. It does not explicitly list when-not-to-use scenarios or name alternative tools, but it provides enough usage context to guide selection.

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