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

Annotations already cover the read-only/idempotent safety profile, yet the description adds substantial context beyond them: result ordering (most-played first), the returned columns, per-row billing, that `limit` caps both rows and cost, and an explicit warning that results are user-generated untrusted content. Billing and trust warnings are exactly the kind of behavioral detail annotations cannot convey.

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?

Four tightly packed sentences, front-loaded with the core action, then alternatives, then return/billing semantics, then a trust caveat. Every sentence carries information an agent needs; none is filler.

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?

Although there is no output schema, the description enumerates the returned fields (pk, user_pk, mix_name, item_total, play_count), the cap semantics, and the cost model. For a two-parameter, fully documented search tool this is complete enough to invoke correctly.

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%, so the schema documents both params. The description still adds meaning: `query` is a case-insensitive substring match on the mix name, and `limit` caps cost as well as row count. It adds value but is not strictly necessary given full schema coverage.

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 states a specific verb and resource (search TikTok playlists/mixes by name) and specifies behavior (case-insensitive substring match, most-played first). It explicitly names two siblings it is not — get_top_tt_playlists for overall ranking and get_tt_playlist_by_id for details — so an agent can distinguish it without opening any schema.

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 gives a concrete use case (find series on a topic) and routes the agent to the correct alternatives with the conditions that select them. Both when-to-use and when-to-use-something-else are stated, leaving nothing to inference.

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