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

Annotations already provide readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds scoping to first-level comments and pagination support, but these are also largely reflected in the schema. No contradiction with annotations.

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, front-loaded sentence that communicates the action, the key identifier, the result scope, and pagination. Every phrase earns its place with no redundant filler.

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 read-only tool with rich input schema descriptions, an output schema, and relevant annotations, the description covers the core behavior. A small gap remains: it does not explicitly address how this tool relates to URL-based or reply-based comment tools, though the name and '一级评论' hint at it.

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 provides detailed semantics for post_id and page_token, including how to obtain post_id and how to handle next_page_token. The description only restates these parameter names without adding information beyond the schema.

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 states a specific verb and resource: '获取一级评论' (get first-level comments) by TikTok post_id, and mentions pagination via page_token. The term '一级评论' distinguishes it from sibling tiktok_get_post_comment_replies, and 'post_id' distinguishes it from URL-based comment tools.

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?

Usage is implied: use this when you have a TikTok post_id and need top-level comments. However, the description does not explicitly state when to choose this over tiktok_get_post_comments_by_url or tiktok_get_post_comment_replies, nor does it name alternatives.

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