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

Goes well beyond the readOnly/openWorld annotations by disclosing credit economics (1 credit for pages with comments, 0 for empty pages and terminal-cursor replays), a distinct comment data source, and the caveat that an empty terminal page does not prove the post has no comments or was deleted. Deducted for the confusing appended claim that "Completed lookups cost at least 10 Nexscope credits," which conflicts with the 1-credit-per-page model stated everywhere else.

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 opening paragraph is repeated verbatim, and the credit/empty-page sentences plus the docs link appear three times. The text also carries pasted marketing boilerplate ("TikTok Comments API View Pricing"), so the signal is buried in duplication rather than front-loaded.

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 no output schema, the description does the work of describing the return shape (`comments` array fields, `total`) and the pagination termination signal. Coverage of edge cases (photo/slideshow posts, separate comment source, empty pages) is thorough; the internal credit contradiction is the main remaining gap.

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 coverage is 100%, so all three parameters are already documented. The description adds only marginal meaning: it clarifies that `cursor` comes from the previous response and must be used until `end_of_pagination=true`, and that `trim=true` responses still cost 0 credits when empty. That is helpful but thin 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?

Opens with a specific verb and resource: "Fetches comments on a TikTok video by URL," and adds the use case (audience reactions, engagement). It does not explicitly differentiate itself from the sibling `social_tiktok_video_comment_replies`, even though it mentions "replies" as a motivation, so an agent could still hesitate between the two.

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?

Operational guidance is strong (paginate with `cursor`, stop at `end_of_pagination=true`, no country parameter), but it never states when to prefer this tool over the replies endpoint or other TikTok siblings. Usage is implied by the input (a post URL) rather than routed explicitly.

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