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

The annotations only declare readOnlyHint=false and openWorldHint=true; the description adds nothing about the fact that this is an open-world, paginated crawl of a third-party API (the pageSize field even mentions internal multi-page pulling). For a 17-parameter tool with no output schema, the description should at minimum explain scope and result shape but does not.

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?

It is short, but the brevity is under-specification rather than efficiency — the single sentence is a title echo that would need to be replaced entirely to be useful. Nothing is front-loaded because nothing substantive is present.

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 17 parameters, a required region, no output schema, and only thin annotations, the description should carry substantial weight but is effectively empty. An agent has no basis from the description alone for deciding whether this is the right video tool or what it will return.

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 one of the 17 parameters (region, pageSize, sortType, videoSortField, duration/time/view filters) is already documented in the schema. The description contributes no additional semantics about their interaction, so the baseline of 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 description is a near-verbatim restatement of the tool name and title: "TikTok Intelligence ET: list Video API." It conveys only that something video-related is listed, with no statement of what is returned, what the listing is scoped to, or how it differs from the many sibling video tools such as nexscope_data_et_list_video_rank or nexscope_data_et_list_product_video.

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 on when to use this tool, when not to, or which sibling to choose instead. An agent cannot infer from the description whether this lists videos for a region, a user, a product, or an ad campaign — the only clue that filtering is possible comes from the schema.

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