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

Annotations already declare readOnly/idempotent/openWorld, and the description adds real behavioral context beyond them: the priced-search cost signal ('the first page is one priced search') and the exact shape of returned items. It stops short of saying how many items a page holds or how pricing scales past the first page.

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 verb and resource are front-loaded in the first clause, and the pricing warning is placed last where it will still be read before invocation. The item-field enumeration is a bit dense but each field named maps to something the agent must know.

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 usefully enumerates the returned item fields and the author, so the agent knows what comes back. The remaining gap is pagination and cost behavior beyond the first page, plus the undocumented `count`/`offset` controls.

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 0%, so the description carries the burden; it does document the important semantics of `source`, `keyword`, `region` (two letters) and `language`. However `count` and `offset` are left completely unexplained, and no format examples are given for region/language, so half the parameter surface is still undocumented.

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 ('Find TikTok videos and image posts for a keyword') and immediately disambiguates the two search modes via the `source` values. It also routes downstream work to analyze_tt_trend_media, so the agent can distinguish it from that sibling without opening a 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?

Explains which `source` value to pick (SEARCH = keyword search, HASHTAG = posts of the named hashtag) and tells the agent to pass the returned `aweme_id`s to analyze_tt_trend_media. There is no explicit 'when not to use' or guidance relative to list_tt_videos, which keeps it below a 5.

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