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

No annotations are present, so the description carries the full burden. It does disclose two genuinely useful traits: the matching behavior is fuzzy/substring (pg_trgm ILIKE) rather than exact, and results are unvalidated user-generated content that should be treated as untrusted input (relevant for prompt-injection handling). It omits result ordering, pagination, and an explicit read-only guarantee.

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 compact sentences, front-loaded with the action and scope, followed by the trust caveat. No filler or repetition of the schema.

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 annotations and no output schema, the description should say more about what is returned (playlist fields, ordering, pagination behavior) to be fully self-sufficient. It covers the safety-relevant trust caveat but leaves return-shape details unspecified.

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 parameters (query, limit) are already documented, including the 1-100 bound. The description only restates that the query targets the mix/playlist name and adds no format guidance (e.g., wildcard or partial-match expectations), so the baseline 3 applies.

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 and resource ("Search TikTok playlists") and a scoping key (mix_name), which separates it from siblings like get_top_tt_playlists and get_tt_playlist_by_id, which retrieve rather than search. It does not explicitly name those alternatives, but the search-vs-retrieve distinction is inferable.

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?

There is no statement of when to prefer this tool over get_top_tt_playlists, get_tt_user_playlists, or get_tt_playlist_by_id. The "search" verb implies lookup when only a name is known, but no condition or exclusion is spelled out.

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