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

Annotations already cover the safety profile (readOnly, openWorld, non-destructive), but the description adds substantive behavior: results come in pages of ~30, a nextPageToken is returned and must be looped to walk history, and the account must be public. It omits rate limits, auth requirements, and failure modes, keeping it below 5.

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 core verb and scope are front-loaded, and the pagination mechanic follows logically. The enumeration of returned fields (likes/comments/shares/plays/collects, cover and playable URLs, music, duration, timestamp) is slightly list-heavy but earns its place given there is no output 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 output schema, the description correctly carries the burden of describing return values and the pagination contract, which it does thoroughly. It lacks edge-case context (empty/private accounts, rate limits), so it is strong but not exhaustive.

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 (handle, nextPageToken) are already fully documented in the schema, including the @ optionality and the first-page omit behavior. The description restates handle and the token but adds no syntax or format detail beyond the schema, 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?

The description states a specific verb and resource (fetch a page of videos for a public TikTok account by handle) and enumerates the returned fields, so the agent knows exactly what the tool produces. It does not explicitly name or contrast the nearby siblings (tiktok_profile, tiktok_search, tiktok_comments), so it falls short of a 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?

It gives concrete use cases (monitor competitor content, track creator engagement, build vetting/analytics datasets) and explains the pagination walk via nextPageToken, which is real guidance. It stops short of stating when NOT to use it or pointing to the profile/search alternative for other intents.

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