TikToks using Song

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

Annotations cover the safety profile (destructiveHint=false, openWorldHint=true, idempotentHint=false), but the description adds genuinely useful context: it consumes paid API credits, requires confirm=true, and clarifies that the read-like POST does not publish to platforms. That credit/confirmation disclosure is the key behavioral fact an agent needs and is not in the annotations.

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 purpose, then return shape, then pagination, then the credit/confirm caveat. Sentences are dense and mostly earn their place, though the aweme_list field enumeration is somewhat long. 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?

With no output schema, the description usefully documents the return payload (aweme_list with aweme_id, desc, statistics, video, author) and the pagination mechanism. Combined with the cost/confirm warning, an agent has enough to invoke and interpret it correctly; only explicit alternative-routing 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?

Schema description coverage is 100%, so the schema already documents clipId, cursor, account, and confirm. The description reinforces clipId and cursor pagination but adds no syntax or format meaning beyond the schema, so baseline 3 is appropriate.

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), resource (TikTok videos using a sound/song), and the key(input clipId). It is distinguishable from siblings like tiktok_get_song_details (song metadata) and tiktok_search_by_hashtag/keyword (different lookup axis).

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 partial guidance: it explains pagination (use cursor from the previous response) and the confirm=true requirement. However, it never explicitly contrasts with alternatives like tiktok_get_song_details or states when this tool is the right choice over them, leaving the routing implicit.

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