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

With no annotations, the description carries the full burden and does disclose genuine behavioral traits: 'Empty results and failures are never charged', the data-fidelity caveat 'Chart miss is degraded catalog songs, not original audio', and the cache hit behavior. These go beyond the schema. The cryptic phrasing of the chart-miss caveat and the garbled template text prevent a 5, but the disclosure substance is strong.

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 short and info-dense at four sentences, with pricing and billing front-loaded after the purpose. But the 'honoured{}' template artifact is a clear defect that should have been cleaned, and 'Chart miss is degraded catalog songs' is awkward, cryptic phrasing. The content earns its place, but the polish is lacking.

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 tool with 8 optional params, no annotations, and no output schema, the description covers pricing, billing on failure, and cache behavior well, but it does not describe the expected result shape at all and the garbled first sentence leaves scope ambiguity. The operational aspects are covered; the data-shape and chart-selection semantics are left to the consumer.

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 baseline is 3 with the schema carrying parameter documentation. The description adds little beyond the schema: 'popular/surging' loosely mirrors rankType, and the cache sentence restates what the schema already says for the cache parameter. The garbled 'honoured{} names applied filters' phrase does not meaningfully clarify how filters act on results.

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 phrase 'Creative Center popular/surging sounds' conveys the core purpose of retrieving TikTok's popular or surging sounds chart, and this is distinguishable from siblings like tiktok_song_details (single song lookup) and tiktok_music_posts (posts using an audio). However, the fragment 'honoured{} names applied filters' is a garbled template artifact that obscures the statement, and the retrieving verb is implied rather than explicit.

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 provides operational context (filters, credits, cache behavior) but never tells an agent when to choose this tool over alternatives such as tiktok_music_posts, tiktok_song_details, tiktok_trending_feed, or tiktok_popular_creators. No sibling is named and no when-to-use/when-not-to-use guidance is given.

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