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

The annotations already establish a read-only, open-world operation, and "(1 credit)" usefully adds a concrete invocation cost not captured elsewhere. Other behavioral details, such as result limits, ordering, or pagination expectations, are not disclosed.

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 exceptionally compact, front-loading the purpose and immediately following it with the credit cost. There is no filler or redundant wording.

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 two-parameter read tool, the description, fully documented schema, and annotations provide enough information to select and invoke it. With no output schema, additional context about returned video data, page behavior, or the workflow from tiktok_song would make it more complete, but these are modest gaps given the tool's low complexity.

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 100%, and both parameters are meaningfully documented, including that cursor comes from the previous page and music_id comes from the song endpoint. The description adds no further parameter formats, constraints, or examples, so it meets the baseline without adding substantial value.

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 clearly identifies the resource and relationship: videos associated with a TikTok sound. It is phrased as a noun fragment rather than an explicit list/get operation and does not differentiate itself from siblings such as tiktok_song or 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 wording implies using the tool when an agent wants videos that use a particular sound, while the schema's music_id description indicates that the ID comes from the song endpoint. The description itself provides no explicit when-to-use, when-not-to-use, or sibling-routing guidance.

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