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

Annotations already declare readOnly/openWorld/non-destructive, and the description adds real value beyond that: the shape of the returned `videos` object, the has_more/max_cursor pagination contract, and a cost warning including that repeated requests may purchase data again. However, the cost statements contradict each other ('at least 10 Nexscope credits' vs '1 credit per request'), which undermines an otherwise informative disclosure.

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 first two sentences are well front-loaded, but the text then repeats itself ('Scrapes the videos in a public TikTok collection. Pass cursor to get more videos.') and appends supplier/pricing boilerplate with two mutually inconsistent credit figures. Roughly half the text is duplicated marketing copy that does not help an agent invoke the tool.

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 two-parameter read tool with no output schema, the description covers return shape, pagination, the public-only constraint, and cost awareness. The only gap is the conflicting pricing information, which leaves the agent uncertain about the real cost of a call.

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%, and the parameters are already documented as 'Public TikTok collection URL' and 'Cursor to get more videos. Use max_cursor from the previous response.' The description restates both almost verbatim, adding only the has_more gating condition, 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 opening sentence gives a specific verb and resource ('Fetches the videos saved in a public TikTok collection') and even resolves the terminology overlap with playlists. It does not explicitly name which sibling tool to use instead (e.g. social_tiktok_profile_videos or social_tiktok_song_videos), so differentiation must be inferred from the word 'collection'.

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?

Clear conditions are given: the collection must be public, pass the collection URL, and page with the previous response's max_cursor only when has_more is true. What is missing is an explicit statement of when to prefer this over other TikTok video-retrieval siblings.

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