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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description adds nothing beyond that: no note on what the call returns, quota/cost implications, or that a videoId from a list endpoint is required. With annotations carrying the burden, this is a minimal-but-not-harmful entry.

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 a single short sentence with zero waste, but it earns no value either: the sentence merely repeats the title and endpoint path. This is under-specification rather than genuine conciseness.

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?

For a five-parameter read tool with no output schema, an agent needs some indication of what a 'video detail' response contains (metrics? creator info? commerce data?) and how it differs from the other video endpoints. None of that is present, leaving the call under-specified despite the decent 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 every one of the five parameters has a documented example (videoId format, region codes, currency, language, dateRange). Nothing in the description adds further meaning, but the baseline of 3 applies because the schema fully documents the parameters.

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 tool's name and title restated: 'TikTok Intelligence KD: video/detail API.' It identifies the platform (TikTok) and resource (video detail), but the phrasing 'video/detail API' is the endpoint path, not an explanation of what data it retrieves. No sibling differentiation against nexscope_tiktok_video_analytics, nexscope_chuhaijiang_tiktok_video_detail, or nexscope_data_kd_video_rank.

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 at all. The many sibling video tools (video_search, video_rank, video_analytics, video_download_url, plus two other vendor-specific video_detail tools) make a routing hint essential, and none is given. The agent must infer usage from the name alone.

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