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

Annotations declare readOnlyHint=false and openWorldHint=true, which is already surprising for a 'detail' read API, and the description does nothing to explain that (credentials? billed calls? rate limits on 1000-item batches?). No behavioral context of any kind is added beyond the title.

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?

One sentence, but the brevity is under-specification rather than efficiency — nothing is front-loaded because nothing is conveyed. It duplicates the title verbatim, so no sentence earns its place.

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?

No output schema exists, so the description is the only place to say what a batch 'video detail' response contains, and it says nothing. For a bulk tool accepting up to 1000 IDs, the absence of any return-value or batching semantics leaves a real gap, only partly offset by the rich parameter schema.

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% and the schema itself explains videoIds/URLs, the 1000 cap, and the merge behavior. The description repeats none of this but the baseline of 3 applies when the schema carries the parameter burden.

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 essentially the title restated: 'TikTok Intelligence ET: batch Video Detail API.' It implies retrieving details for multiple videos, but it never says what 'detail' returns (stats, creator, product links) and does not distinguish it from siblings like nexscope_data_et_list_video or nexscope_data_et_get_video_download_url.

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?

No when-to-use guidance, no exclusions, no mention of alternatives. With dozens of TikTok/ET siblings (list_video, get_video_download_url, batch_product_detail), an agent has no signal telling it why to pick this one or what input source to use.

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