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

Annotations only cover read-only/open-world, and the description adds real behavioral context: newest-first ordering, inclusion of photo posts typed as `image` or `carousel`, per-page cap with cursor paging, and a 1-credit cost. One flaw: it claims "Up to 15 per page" while the schema says count defaults to 35 / max 35, leaving the agent unsure of actual page size.

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?

Five short sentences, front-loaded with the purpose, then return contents, content types, pagination, and cost — each carrying distinct information. Minor redundancy between the title line and "A creator's public posts," and the page-size figure adds noise given its conflict with the 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 does the right work by summarizing what comes back (counts, media typing), how to page, and the credit cost. The incomplete/contradictory page-size statement is the only meaningful gap for a four-parameter read tool.

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 75%, so the baseline is 3; the description reinforces `cursor` ("pagination.cursor from a previous response") and page-size behavior. However, its page-size claim conflicts with the schema's count description, and `cache_max_age` remains undocumented in both places.

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+resource (videos posted by a creator) and clarifies scope with "A creator's public posts, newest first." It implicitly distinguishes itself from hashtagVideos/songVideos/playlistVideos by tying the listing to a creator, though no sibling is named explicitly.

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?

There is no statement of when to use this versus tiktok_profile, tiktok_video, or the other video-listing siblings, and no exclusions or prerequisites. The only usage-adjacent detail is that a cursor fetches older posts, which is pagination mechanics rather than tool selection guidance.

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