tiktok_posts

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states only that it returns posts with optional pagination/sort, but does not mention response format, pagination mechanics (e.g., whether a next cursor is returned), rate limits, or any side effects. For a read operation, this is minimal and fails to inform the agent about how pagination actually works or what to expect in the output.

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 short and front-loaded with the core purpose. However, it contains redundancy: 'Retrieve posts from a TikTok profile' and 'Returns posts from a TikTok profile' repeat the same idea. This could be condensed, but overall it is efficient and not overlong.

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?

For a tool with no output schema and no annotations, the description is insufficient. It does not explain the structure of the returned posts (e.g., list of objects, fields), nor how cursor pagination works (whether the response includes a next cursor). The agent would need to guess or inspect sample data. More detail on output and pagination flow is necessary for correct 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%, with each parameter already described ('Pagination cursor', 'Sort mode: 0 latest, 1 popular, 2 oldest'). The description adds that cursor and sort_type are optional, but this is implied by the schema's required list. It does not add meaning beyond what the schema provides, so the baseline of 3 is appropriate.

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 ('Retrieve posts') and the resource ('TikTok profile'), and specifies the key identifier (secUid). It distinguishes from siblings like tiktok_profile (profile info) and tiktok_post (single post) by using plural 'posts' and mentioning pagination/sort. No tautology or vagueness.

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 usage (retrieve all posts from a profile) but does not explicitly contrast with alternatives such as tiktok_post or tiktok_profile, nor provide when-not-to-use guidance. The agent must infer the distinction from the name and schema, which is not ideal given the large sibling set.

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