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

Goes well beyond readOnlyHint/openWorldHint: discloses ordering (TikTok's own ranking), the hard 60-comment cap, absence of reply threads, empty-list-with-total-0 behavior for unknown or deleted video IDs, and a full pricing/billing model ($0.002 USDC per successful call via x402, failures not charged). The cost and failure-charging details are exactly the kind of pre-call context an agent needs.

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?

Front-loaded with the resource and return fields, then scope limits, then edge-case behavior, then price. Four dense sentences with no filler, though the 'up to 60' phrasing mildly duplicates the schema's limit range.

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 an output schema present, the description need not explain return shape, and it still names the key fields and the total-count field. Combined with annotations and 100%-covered params, an agent has everything needed to decide, call, and anticipate cost and empty results.

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%, so both params (url, limit) are already documented, including the 1–60 range and default of 20. The description corroborates the 60 ceiling and clarifies that the URL must be a public video or numeric ID, but adds no new syntax or format detail beyond the schema. 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?

States a precise verb+resource: top-level comments of a public TikTok video, and enumerates exactly what is returned (comment ID, text, likes, reply count, time, language, flags, commenter fields, total count). It is unambiguously the TikTok single-video comment tool, distinguishable from social_tiktok_profile, social_tiktok_hashtag_analytics and social_youtube_comments.

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?

Gives clear context for when it applies: public videos only, top-level comments only ('no reply threads'), and a stated cap of 60. It does not name an alternative sibling for reply threads or for other TikTok surfaces, so routing is inferred from scope rather than explicit signposting.

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