get_tiktok_user_posts

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

No annotations are provided, so the description carries full burden. It discloses output fields (ID, caption, timestamp, stats), pagination behavior (cursor, has_more), and a dependency (profile endpoint). It does not cover rate limits or error handling, but for a read-oriented tool, this is adequate.

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?

Two sentences, front-loaded with the core purpose and output format, followed by essential usage context. Every sentence is valuable and there is no redundancy.

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 4 parameters, no output schema, and no annotations, the description explains the prerequisite, pagination pattern, and output fields. It does not cover sort_type enum values (schema does) or all edge cases, but it is complete enough for typical usage.

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 100%, so the baseline is 3. The description repeats some schema info (e.g., 'requires sec_user_id') but adds pagination context. It does not add new parameter-specific meaning beyond the schema descriptions.

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 explicitly states 'List a TikTok user's videos with pagination as JSON', providing a specific verb and resource. It distinguishes from siblings like get_tiktok_profile (profile info) and get_tiktok_video (single video) by focusing on listing multiple posts with pagination.

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 clearly explains the prerequisite ('Requires sec_user_id from the profile endpoint') and gives explicit pagination instructions ('Use data.max_cursor for next page; stop when data.has_more is 0'). It does not compare to alternatives like search_tiktok_videos but provides sufficient guidance for proper usage.

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