Collection Videos

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

Adds real context beyond the annotations: it warns that the call may consume paid API credits, requires `confirm=true`, and clarifies that read-like POST requests do not publish to social platforms (reconciling with readOnlyHint=false). It does not quantify credit cost or discuss failure modes, but the safety/cost profile is well disclosed.

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-loads what the tool does, then return format, then pagination, then cost/confirm caveats. Dense but every sentence carries useful information; minor verbosity in the credit/confirm sentence.

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 steps in to name the returned fields and explains pagination, which is what an agent needs. It omits error handling and the exact cost of a credit-consuming call, but is otherwise complete for this four-parameter fetcher.

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 parameter documentation largely lives in the schema. The description still adds value by tying `cursor` to the prior response's `max_cursor` and gating it on `has_more`, giving pagination semantics the schema alone only partially conveys.

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 specific verb (fetches) and resource (videos saved in a public TikTok collection/playlist), and describes the return shape (`id`, `desc`, `author`, `stats`, `video`). This clearly distinguishes it from siblings like tiktok_profile_videos or tiktok_video_info.

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 explicit operational guidance: pass the collection URL, and paginate by passing the previous response's `max_cursor` as `cursor` when `has_more` is true. It does not explicitly say when to prefer this over sibling tools (e.g., profile videos), but the context is clear enough to invoke correctly.

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