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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description adds no behavioral context of its own: it does not mention pagination caps, rate limits, data freshness, or which regions are supported. It does not contradict the annotations, but it contributes nothing.

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 text is a single short sentence, but its brevity comes from under-specification rather than conciseness. There is nothing about scope or required inputs, and no usable information is front-loaded beyond the title itself.

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?

This is an eight-parameter listing tool with required date, rankType, region, and videoRankField, and no output schema. The description supplies none of the context an agent needs—what a row contains, how ranking is defined, or how results are paged—so it is inadequate for the complexity.

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 eight parameters—date format, region enum, pageNum/pageSize, rankType, videoRankField, createdByAi, and productCategoryId—are documented in the schema. Per the baseline rule, a score of 3 applies when the schema does the heavy lifting and the description adds no meaning.

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 only restates the title: 'TikTok Intelligence ET: list Video Rank API.' It does name a resource (Video Rank list) on TikTok, but it gives no scope, no fields, and no way to distinguish it from siblings such as nexscope_tiktok_video_rank, nexscope_data_kd_video_rank, or nexscope_data_et_list_video. This is close to tautology, with only a small amount of platform-level information added.

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?

There is no guidance at all about when to use this tool versus alternatives. The sibling list contains several closely named video-rank and video-list tools (nexscope_tiktok_video_rank, nexscope_data_kd_video_rank, nexscope_data_et_list_video), and the description does nothing to help select among them.

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