Search by Keyword

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

Annotations only cover the safety profile (readOnlyHint=false, openWorldHint=true, idempotentHint=false, destructiveHint=false). The description adds substantial context beyond them: paid credit consumption, the confirm=true gate, cursor pagination semantics, and the warning that TikTok may return duplicate results years beyond what annotations convey.

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?

Front-loaded with the core purpose, then return shape, pagination, and cost caveats in a logical order. Slightly dense with the nested field enumeration, but every sentence carries operational value and nothing is wasted.

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 carries the return-value burden well by naming search_item_list/aweme_info and its key fields, and it covers pagination, duplicate behavior, and the credit/confirm mechanics. Nothing essential for correct invocation is missing.

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 every parameter (including the region proxy, sort_by/date_posted enums, and confirm) is already documented in the schema. The description only reinforces pagination via 'Paginate with cursor', adding minimal meaning beyond structured fields, so 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?

States a specific verb (Searches) and resource (TikTok videos by keyword), and explicitly frames it as 'the general video search across all of TikTok', which distinguishes it from siblings like tiktok_search_by_hashtag, tiktok_search_users, and tiktok_search_suggestions without opening any schema.

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 'the general video search across all of TikTok' gives clear context that routes the agent away from hashtag/user search variants, and it flags credit consumption and the confirm=true prerequisite. It stops short of naming a specific alternative tool or stating explicit when-not-to-use conditions, so it is clear context rather than full routing guidance.

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