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

Annotations already declare readOnlyHint, openWorldHint, and destructiveHint=false, so safety is covered. The description adds genuinely useful non-annotation context — credit cost, that repeated requests may repurchase data, and the exact shape of the returned aweme_list — but the cost section is internally contradictory ('at least 10 Nexscope credits' versus '1 credit per request'), which weakens the disclosure.

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 two sentences are efficient and front-loaded, but the trailing pricing block is scraped boilerplate with repeated and conflicting statements ('TikTok Trending Feed API View Pricing Get the trending feed from TikTok', 'Examples are not guaranteed prices'). Roughly half the description is noise that dilutes the useful content.

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 compensates well by enumerating the returned fields (aweme_id, desc, statistics counters, video URLs, author, image_post_info). For a two-parameter read it is nearly complete; the only real omission is any indication of result volume or pagination, and the muddled cost section.

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 `region` and `trim` are already documented, and the schema even clarifies that region is a proxy location rather than a strict content filter. The description adds nothing about either parameter, so the baseline of 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?

The description opens with a specific verb and resource: 'Fetches TikTok's trending/For You feed for a given region,' which is distinct from siblings like social_tiktok_search_keyword or social_tiktok_video_search. It does not explicitly name an alternative, but the 'trending/For You' framing is enough to tell what kind of feed this is.

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 an implied use case ('useful for discovering viral content and what's currently popular') but never says when to prefer this over a keyword search or a hashtag search, nor any prerequisites. The usage context is inferable rather than stated.

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