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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered. The description adds two genuinely useful facts beyond that: results are ordered by most-liked first, and each call costs 1 credit. It omits pagination behavior even though a cursor parameter exists, and the phrase "comments on a video" is mildly ambiguous on its own but not contradictory to the read-only hint.

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?

Single compact sentence with the sort order front-loaded and the credit cost appended in parentheses; nothing is wasted. It is arguably too terse for the missing context, but the structure itself is clean.

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?

This is a simple two-parameter read tool with annotations and a fully documented schema, so the bar is modest. Still, it lacks any note on pagination via cursor or the shape of returned comment data, which would help an agent chain pages correctly.

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%, with both url and cursor fully documented in the schema, so the baseline is 3. The description adds only the ordering implication of "most liked first" and does not clarify cursor behavior or URL format beyond what the schema states.

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?

"Comments on a TikTok video, most liked first" names the resource and the sort order, but it is a noun phrase with no verb, so the agent must infer that this retrieves rather than posts comments. It also does not distinguish itself from the sibling tiktok_comment_replies, which handles a closely related resource.

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 explicit when-to-use guidance and no mention of alternatives such as tiktok_comment_replies or tiktok_video. The agent must infer the retrieval scenario 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.