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

Annotations declare readOnlyHint=false and openWorldHint=true; the description adds genuinely useful operational context (no automatic retries, no automatic pagination, preserve provider fields and metric units). It does not, however, address authorization needs, rate limits, or what the response contains. No direct contradiction with annotations is stated.

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?

Three short front-loaded sentences with no padding, and the pagination caveat appears early. Some of the wording is boilerplate provider policy rather than tool-specific information, which keeps it from a 5.

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 16 parameters, no output schema, and two partially opaque enum parameters, the description does not do enough: it never describes the result shape, the sort behavior, or how filters interact. An agent could invoke it, but would be guessing about what comes back and how to page through results.

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 all 16 parameters are already documented, establishing the baseline of 3. The description adds no field-level meaning beyond the schema — for example, it does not clarify accountType (0/3/4), the unpublished sort/category enums, or how the min/max metric filters combine.

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 restates the title ('TikTok Video Keyword Search') without adding a distinct verb/resource framing or scope. It never differentiates this tool from close siblings such as nexscope_tiktok_video_rank, nexscope_tiktok_video_analytics, or nexscope_chuhaijiang_tiktok_video_detail, so the agent must infer the difference from names 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?

'Execute only this operation; no automatic retries or pagination' is an execution constraint, not guidance on when to choose this tool over alternatives. There is no mention of when to use a keyword search versus a detail, rank, or analytics endpoint.

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