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

Beyond the readOnly/destructive annotations, the description discloses important behaviors: pagination is cursor-based and cursors are opaque, duplicate results are preserved, media links are temporary, and every successful page costs 0.2 account credits. This is substantial added context.

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, front-loaded with the core operation, and every sentence carries distinct information (pagination, duplicates, media link lifetime, credit cost). No filler or redundancy.

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 paginated list tool with an output schema, the description covers the key operational details: paging, cursor opacity, duplicate preservation, temporary links, and cost. Nothing essential to calling the tool correctly is missing.

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 schema only documents music_id; the cursor lacks a semantic description. The description partially compensates by explaining that cursor calls must continue with the same music_id and that cursors are opaque, which is meaningful information beyond the schema. It does not fully specify first-page behavior or how to obtain next_cursor.

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 description states a specific verb and resource: 'Fetch one page of videos using a sound clip music_id.' This clearly identifies the tool's scope and differentiates it from sibling list tools such as list_tiktok_hashtag_videos and list_tiktok_profile_videos.

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?

The description gives clear context for when the tool applies: when you have a sound clip music_id and want a single page of its videos. It also gives pagination instructions ('Continue with next_cursor and the same music_id'), though it does not explicitly name alternative tools or exclusion cases.

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