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

No annotations are provided, so the description carries the full burden. It does disclose pricing ('Costs 1 credit(s), priced per page'), the auth requirement (Bearer API key), and the credit unit, which is genuinely useful. It doesn't explain rate limits, what happens on empty results, or the response shape.

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 definition is short and front-loads the purpose, but it reads as machine-appended metadata fragments ('Platform=tiktok resource=search. Credits unit: page.') rather than a coherent sentence structure.

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 output schema and no annotations, the description should do more to explain return values and result behavior. It covers cost and auth but leaves the response shape and pagination outcome unstated.

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 schema already explains keyword and cursor. The description adds no parameter guidance beyond the schema, but the 'Priced per page' line does hint at the pagination semantics of the cursor. Baseline 3 is appropriate.

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 public users by keyword.' It's clear what the tool does, and the Platform=tiktok tag distinguishes it from sibling search tools like threads_search, reddit_search, and youtube_search. It doesn't explicitly name a sibling alternative, so 4 rather than 5.

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 word 'public' implies a scope, but there's no explicit guidance on when to use this versus alternatives like tiktok_user or tiktok_posts. Usage context is only implied.

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