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

Beyond the annotations (readOnlyHint=false, openWorldHint=true) the description adds genuinely useful operational facts: a single request per call with no automatic retry or pagination, and an instruction to preserve raw provider fields and metric units rather than normalizing them. It does not, however, say what data the detail response carries or how the read behaves, so the disclosure remains partial.

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?

Only two sentences and no padding beyond the redundant title repeat, which occupies the front-loaded position with zero informational value. The substantive constraints are compressed into one dense sentence.

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?

There is no output schema, three parameters, and a sparse annotation set, yet the description never says what the detail payload contains, what the `include: core` expansion yields, or how the fields should be presented. For a detail/retrieval tool with no return documentation, this leaves major gaps.

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 the id/country/include semantics are already fully documented in the schema (including that id comes from the search operation and that country_code may differ). The description adds nothing about parameters, which is acceptable but earns only the baseline.

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 first sentence just restates the tool name and title ("TikTok Video Detail") without a verb or statement of what is retrieved. It does not distinguish this from the many closely named siblings such as nexscope_chuhaijiang_tiktok_video_search, nexscope_chuhaijiang_tiktok_video_related_products, or nexscope_data_kd_video_detail.

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 about when to choose this tool. Nothing says to call this after video_search, nor when to prefer it over video_search/related_products/reviews.

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