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

Annotations already provide safety hints (readOnlyHint=true, destructiveHint=false), and the description adds significant behavioral context: pagination returns one page, media URLs are temporary, successful responses support dataset piggybacking, content resolves against US region, and requests are metered. This goes well beyond what annotations alone convey.

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 compact and front-loaded, leading with the core action and then adding essential operational caveats. Every sentence adds value, and there is no redundant restating of the title or schema.

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 output schema exists and the tool's complexity is moderate, the description covers all important operational aspects: pagination, ordering options, temporary media URLs, regional resolution, piggybacking eligibility, and metering. An agent has enough context to invoke it correctly and interpret behavior.

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 0%, so the description must carry parameter meaning. It explains username as the video target, cursor as the pagination token from the previous response, sort_by as latest or popular ordering, and region as fixed to US. This fully compensates for the absent 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 clearly states the tool fetches one cursor-paginated page of TikTok videos for a given username, with explicit verbs and resource scope. It is easily distinguished from sibling tools like get_tiktok_profile or get_tiktok_video by focusing on listing profile videos.

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 provides clear operational guidance: use the returned cursor to paginate, choose latest or popular ordering, and expect metered live-data behavior. It does not explicitly name alternatives or say when not to use this tool, but the context is sufficiently clear for an agent to know when this tool applies.

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