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

Annotations already declare readOnlyHint=true, openWorldHint=true, destructiveHint=false, so safety is covered. The description adds genuine non-schema context: no automatic retries, no pagination (one call, one record), and an instruction to preserve provider fields and metric units verbatim. It still says nothing about rate limits, failure modes, or what the payload contains.

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?

Three short sentences with no padding, and the operational constraints are front-loaded after the title. Only the first sentence is wasted, being a verbatim restatement of the tool name.

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 no output schema, the description carries the burden of describing what comes back, and it only gestures at this via "preserve provider fields and metric units." For a simple 3-param read tool whose schema and annotations are rich, this is minimally adequate but leaves the agent guessing about the detail payload's shape.

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% — `id`, `country` enum, and `include` expansion are all documented in the schema, including the string-precision and country_code caveats. The description contributes nothing additional about parameters, 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 opens by restating the tool title ("TikTok Video Detail"), which adds no information beyond the name. Combined with the name and required `id`/`country` params an agent can infer it fetches one video's detail, but the description never says so explicitly nor distinguishes it from siblings like nexscope_chuhaijiang_tiktok_video_search or nexscope_chuhaijiang_tiktok_video_reviews.

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 invocation hygiene, not routing guidance. There is no statement of when to use detail vs. video_search or video_related_products, and no prerequisite about obtaining the `id` from a search call (that hint lives only in the schema).

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