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

Annotations declare readOnlyHint=false and openWorldHint=true, but the description says nothing about behavior: no cost/quota, no rate limits, no data freshness, no indication that this is effectively a query against an external ranking provider. Because the annotation profile is sparse and arguably surprising for a 'list' operation, the description carries the full burden and delivers 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?

A single short sentence, so nothing is bloated, but it is entirely redundant with the title and front-loads nothing useful. Brevity here is under-specification rather than efficiency.

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?

An 8-parameter ranking-query tool with no output schema and no annotations covering semantics needs the description to explain what the ranking result contains and how rankType/videoRankField interact. None of that is present; only the schema parameters survive as usable information.

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% — every one of the eight parameters (date, region, rankType, videoRankField, productCategoryId, createdByAi, pagination) is documented in-schema with formats and allowed values. The description adds no parameter meaning, but the baseline of 3 applies when the schema does all the work.

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 Intelligence ET: list Video Rank API') without expanding on what a 'Video Rank' is or what is returned. A reader learns only that it lists something ranking-related for TikTok videos — the name already conveys that much, so no value is added and no sibling (e.g. nexscope_tiktok_video_rank, nexscope_data_et_list_video) is distinguished.

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 on when to use this tool versus the many adjacent TikTok/ET siblings such as nexscope_data_et_list_video or nexscope_tiktok_video_rank. No preconditions, no exclusions, no alternative named.

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