tiktok_posts: GET /

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

With no annotations available, the description carries the behavioral disclosure burden. It accurately conveys read-only intent, reports the approximate page size, and clearly explains pagination via nextPageToken to walk the account history. It does not mention credential boundaries or rate limits, but those are not central to this read-only API.

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 description is only three sentences and is front-loaded with the main action, followed by return fields, pagination, and use cases. The returned-field enumeration is slightly long, but each clause adds factual value, making the description efficient rather than padded.

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?

Given the small parameter count and the absence of an output schema, the description provides a strong, actionable mental model of the tool's behavior: input handle, page size, returned video fields, and pagination. It does not show an explicit response example or error conditions, but those are not necessary for a basic fetch-and-paginate workflow.

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?

The schema already documents both parameters completely (100% coverage), so the description does not need to add detailed parameter semantics. It does add the useful note about passing the nextPageToken back for pagination, but this is a modest enrichment rather than a fundamental explanation.

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 clearly states the action and resource: fetching a page of videos for a public TikTok account by username, then enumerates the returned content fields. This distinguishing account-scoped focus separates it from the sibling tools focused on comments, profile info, or search.

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?

The description explicitly names intended use cases, such as monitoring competitor content, tracking creator engagement, and building datasets for analytics. It does not explicitly state when not to use it or how it compares to the sibling tools, so it misses out on the top score.

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