Get a sample of the newest public NudiTok videos (max 20).
| Name | Required | Description | Default |
|---|---|---|---|
| page | No | Page number (1-based) | |
| cursor | No | Opaque pagination cursor from a prior call | |
| per_page | No | Items per page (max 20) |
| Name | Required | Description | Default |
|---|---|---|---|
| count | No | ||
| videos | No | ||
| has_more | No | ||
| next_cursor | No |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the full burden of disclosing behavior. It adds useful context that the feed is a sample, is limited to public videos, and is ordered by newest. However, it does not disclose pagination behavior, defaults, authentication needs, or what happens when cursor vs. page is used.
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 a single, front-loaded sentence with no filler. Every word earns its place: action, resource, ordering, visibility, and limit are all conveyed efficiently.
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?
The tool is simple and has an output schema, so return values need not be explained. Still, the description leaves gaps around pagination defaults, whether page and cursor are alternative mechanisms, and what 'sample' precisely means for the result set, which an agent would need to infer.
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 the baseline is 3. The description adds no parameter-specific meaning beyond repeating the 'max 20' constraint already present in the per_page schema; page and cursor semantics come entirely from the schema.
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 a specific verb ('Get'), a specific resource ('newest public NudiTok videos'), and a key constraint ('max 20'). This distinguishes it from siblings like get_trending, get_user, get_video, and search_content without ambiguity.
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 implies when to use the tool: when you need the newest public videos rather than trending, user-specific, or search-driven results. However, it does not explicitly name alternatives or state when not to use this tool, leaving usage guidance mostly implicit.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool targets a distinct data type or access pattern: feed, trending, user, video, creators, tags, and search. The only mild overlap is between get_feed and get_trending, but their descriptions clearly separate 'newest' from 'trending by engagement.'
Tool names mostly follow a consistent verb_noun pattern with get_ for single/current items and list_ for directory-style browsing. get_feed and get_trending use get_ for collection-style endpoints, which is a slight deviation from the otherwise clear list_ convention for collections.
Seven tools is a well-scoped size for a read-only content browsing API. Each tool covers a meaningful content surface without redundancy or bloat.
The surface covers the core browsing workflows: discovering videos via feed/trending/search, inspecting users, videos, creators, and tags. Minor gaps exist such as no per-tag detail endpoint and no comment access, but these are acceptable for a public read-only client.
