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

Annotations already cover readOnly/safe/openWorld, so the description correctly spends its words on the return shape (id, desc, content_type, statistics, video, images), the cursor-based pagination, and the duplicate-results caveat — all genuine behavioral value beyond structured fields. However, the cost disclosure is internally contradictory ('at least 10 Nexscope credits' versus '1 credit per request'), and the trailing supplier-pricing boilerplate muddies rather than clarifies what a call costs.

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 first sentence is well front-loaded, but the text then repeats the duplicate-results warning three separate times and appends SEO-style copy ('TikTok Top Search API View Pricing Search TikTok Top results...') plus contradictory credit statements. Substantial trimming would improve it without losing information.

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, the description steps in to enumerate the returned fields and note pagination, which is what an agent needs to consume results. The only gap is the inconsistent pricing statement, which leaves the cost model ambiguous even though safety and shape are adequately covered.

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 query, cursor, region, sort_by, and publish_time are already fully documented with their enums. The description only restates pagination ('Paginate with cursor') and adds no new syntax, defaults, or constraints. Baseline 3 is appropriate when the schema carries the semantics.

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 opening sentence names a specific verb and resource ('Searches TikTok's Top results by query') and immediately differentiates it from the keyword-search sibling by noting it also returns photo carousels. An agent can confidently select this over social_tiktok_search_keyword without opening the 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 clearly states the condition that selects this tool ('returns both videos and photo carousels, unlike keyword search which only returns videos'), which is an implicit routing rule. It never names the sibling tool exactly or says when NOT to use this one, so it falls short of an explicit alternative/enumeration.

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