TikTok Channel Videos API

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

Beyond the readOnlyHint annotation, the description adds concrete behavioral details: 2 credits on live reads, 0 on cache hits, public-data-only scope, pagination via nextCursor, and platform-specific field naming. It aligns with annotations rather than contradicting them.

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 description is compact and front-loaded, with each sentence serving a purpose: purpose, return shape, cost, data scope, and read-only status. No filler or repetition beyond a minor redundant 'Read-only' tag.

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?

Without an output schema, the description provides a reasonable shape: a page of items plus nextCursor. It explains the data scope and cost, though it does not enumerate item fields; this is acceptable given the schema covers all input parameters.

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?

The input schema already provides 100% coverage with descriptions for url, cache, limit, and cursor. The description adds little parameter-level detail beyond reinforcing the cursor/nextCursor pagination relationship and the platform-specific field names.

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 and resource: 'Returns a page of recent public videos for a TikTok account.' It also distinguishes itself from likely siblings like tiktok_stats and tiktok_profile by focusing on paginated video items rather than stats or profile details.

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 context is provided: use this for recent public TikTok videos with cursor pagination. It also implicitly warns against use when bios, contact details, or login-walled data are needed, and notes the cost difference between cache hits and live reads.

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