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

Annotations already declare readOnlyHint=true and openWorldHint=true, covering the safety profile. The description adds pagination context ('continue with the returned cursor'), but this is largely redundant with the cursor parameter's schema description and does not disclose anything about error handling, rate limits, or what the listing contains beyond the channel scope.

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?

Two short sentences, front-loaded with the primary purpose and followed by the key usage instruction. No unnecessary words or tangential details.

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 simple read-only list tool with full schema coverage, an output schema, and annotations covering safety, the description is largely complete. It could mention that mv_id comes from a TikTok video object (though the schema already says so), but nothing essential is missing for correct invocation.

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 both mv_id and cursor are already well documented in the input schema. The description merely restates that an mv_id is needed and a cursor continues pagination, adding no meaningful semantic detail beyond what the schema provides.

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 (List) and resource (videos in a TikTok music-video channel), making the core action clear. It does not explicitly differentiate from sibling tools like tiktok_mobile_music_posts or tiktok_mobile_music_related, leaving some ambiguity about when this channel-specific listing is preferred.

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 says 'Pass an mv_id and continue with the returned cursor,' which gives direct parameter usage but offers no guidance on when to use this tool versus alternative TikTok music or video listing tools. Usage is implied rather than contrasted with siblings.

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