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

Beyond the readOnly/openWorld annotations, the description discloses two genuinely useful behaviors: it requires a configured TikTok signer (a hard prerequisite that causes failure if unmet) and it costs 1 credit (a cost signal). It omits pagination semantics despite a cursor parameter, but the prerequisite and cost details materially help correct invocation.

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?

Very short and front-loaded, with prerequisites and cost at the end where an agent will still see them. Minor redundancy: 'Videos in a playlist' and 'The videos inside one TikTok playlist' largely repeat the same fact.

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 read-only, annotated, no-output-schema tool, the description covers purpose and prerequisites adequately. However, it does not describe pagination behavior (the cursor/count parameters imply paging), page size limits, or result shape, leaving gaps an agent would need to reason about.

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 75%, with count, cursor, and playlist_id documented in the schema. The description adds only one non-schema semantic detail — result ordering follows the creator's chosen order — and says nothing about cache_max_age, the undocumented parameter. Baseline 3 is appropriate when the schema does most of the work.

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+resource: retrieves the videos inside a single TikTok playlist, including that they come back in the creator's chosen order. It is clear what the tool returns, though it never explicitly contrasts with the sibling tiktok_playlists (which lists playlists rather than their contents).

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?

No statement of when to use this vs. alternatives like tiktok_playlists, tiktok_userVideos, or tiktok_hashtagVideos. The only guidance is an operational prerequisite (needs a configured signer), not a usage/exclusion condition. The agent must infer the selection rule from the name.

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