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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety bar is low. The description still adds real behavior: the default scope when q is absent (account's previously used music), that previews play from TikTok, and that omitting a music_id delegates selection to TikTok at launch — none of which is in the annotations or schema.

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?

It is short, but the opening two clauses restate each other and the grammar is broken in several places ("image ads run with a music", "the musics this ad account used"), which slows parsing. The most decision-relevant facts — keyword vs. account history, and the music_id hand-off — are present but not front-loaded.

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 carries the return burden and does so adequately: it says each item yields a music_id and that previews are hosted by TikTok. For a simple three-parameter read tool this is close to complete; only pagination behavior for page and the other returned fields are left unstated.

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 67%, a mid-range baseline. The description genuinely adds meaning for q (a keyword with an example, and the fallback behavior when omitted) and implicitly for ad_account_id through the launch context. However, page is undocumented in both schema and description, and no format or pagination semantics are given.

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 names a specific verb and resource — music from TikTok's carousel library available to a launch — which is unambiguous against siblings like list_tiktok_posts or list_platform_templates. It is not a tautology of the name, but the phrasing is garbled ("the music of TikTok's carousel library a launch can use", "the musics") so the intent takes a second read.

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?

It states the key usage fork clearly: pass q for a keyword search (e.g. "upbeat"), omit it to get the music this ad account has already used. It also tells the agent what to do with the result (feed music_id into prepare_launch tiktok.ad_settings.music_id) and what happens if nothing is chosen (TikTok picks per carousel). No explicit when-not-to-use against alternatives, but no sibling serves this purpose.

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