Profile Videos

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

Annotations declare readOnlyHint=false and destructiveHint=false, which alone is confusing for a POST; the description resolves this by stating it consumes paid API credits, requires confirm=true, and that read-like POSTs do not publish to platforms. That is genuine value beyond the structured hints, though rate-limit or retry behavior is not covered.

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?

Front-loaded with purpose and sortability, then return shape, then pagination and troubleshooting. Dense and mostly waste-free, though the return-field enumeration (aweme_list, statistics sub-keys) is lengthy for a tool with no output schema and could be trimmed.

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 compensates by naming the top-level return key and key nested fields, and it covers pagination, region fallback, and credit/confirm behavior. Only minor gaps remain, such as how handle vs user_id affect performance beyond the schema note.

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 handle, region, max_cursor, sort_by, account, confirm, and trim are all documented in the schema itself. The description restates region fallback and cursor pagination but adds no syntax or format detail beyond what the schema already provides; baseline 3 applies.

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 and resource ('Fetches videos posted by a TikTok user') plus the ordering options, which distinguishes it from tiktok_profile (profile metadata), tiktok_video_info (single video), and tiktok_collection_videos (collections) without opening any schema.

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?

Gives clear intended use ('get a creator's video feed or TikToks') and concrete operational guidance (paginate with max_cursor, retry with region=US when a profile unexpectedly returns nothing). It stops short of naming which sibling to use instead for adjacent needs, so no explicit exclusions.

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