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

No annotations are provided, so the description carries more burden. It usefully discloses returned content (title, engagement counts, author info, cover/music), which helps because there is no output schema. However, it omits authentication requirements and does not explicitly state read-only behavior, so it only partly covers the behavioral context.

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?

The description is a single compact, front-loaded phrase with a colon-separated field list and no filler. It is appropriately terse, though not structured enough to warrant a 5.

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 simple video-detail tool with full parameter schema coverage and no output schema, the description gives a useful partial list of returned fields. It still omits usage guidance and authentication context, and the return values are only examples ending in 等, so it is minimally adequate rather than complete.

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 already documents aweme_id as the video ID and _token as an alternate auth token. The description adds no additional parameter meaning, so the baseline 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 names a specific resource, 抖音视频详情, and lists return fields such as 标题/点赞/评论/分享数、作者信息、封面音乐, so an agent can identify it as video-metadata retrieval rather than comments. It does not explicitly distinguish itself from siblings like douyin_video_comments or douyin_search, so it falls short of a 5.

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 when-to-use guidance, no alternatives named, and no prerequisites. The label implies retrieving video details, but an agent must infer when to choose this over douyin_video_comments, douyin_search, or douyin_author.

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