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

Annotations already declare readOnlyHint=true, openWorldHint=true, destructiveHint=false, so the safety profile is covered and the bar is lower. The description adds genuine value by disclosing the returned metric set (views, likes, comments, shares, favorites, sales, GMV) since there is no output schema, but it says nothing about data freshness, per-call cost, rate limits, or the 10-per-page third-party API round-merging behavior that materially affects result behavior.

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 first sentence is well front-loaded and information-dense, but the second paragraph is a repetitive keyword dump that restates the same phrases twice ('TikTok video search, TikTok video list, TikTok promotional videos...' appears nearly verbatim in both halves). Roughly half the description is duplicated trigger spam that consumes budget without adding discriminative signal.

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 17-parameter tool with only one required field and no output schema, the description usefully covers both the filter surface and the return fields an agent would otherwise not know. Gaps remain around pagination behavior beyond what the schema states, result ordering defaults, and how it differs from sibling video tools, but the core call decision is supported.

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 enum-like value mappings for sortType, videoSortField, isAd, salesFlag, and the string-only quirk of createdByAi, so the schema carries the semantic load. The description only echoes the filter categories already documented in the properties, adding no extra syntax or range guidance beyond what the schema provides; 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 names a specific verb (search and analyze) plus the resource (TikTok video data) and enumerates the filter dimensions and returned metrics, which is far more than a restated title. It does not, however, distinguish itself from near-identical siblings such as nexscope_chuhaijiang_tiktok_video_search, nexscope_tiktok_video_analytics, or nexscope_tiktok_video_rank, leaving an agent unable to pick between them from the description alone.

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 trigger paragraph gives situational context ('when users mention TikTok video search...') and broadens activation to non-explicit mentions, which is usable guidance. But it is keyword enumeration rather than discrimination: there is no statement of when NOT to use this tool, no prerequisites, and no routing to the many overlapping TikTok video siblings, so an agent still has to guess among near-duplicates.

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