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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds genuine behavioral context beyond that: the newest-first ordering, the fields returned per video, and a cost of 1 credit per call. It stops short of describing pagination or result volume, which the schema only partially covers via the cursor parameter.

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?

One dense sentence plus a cost marker, with the resource and ordering front-loaded and no filler. Every clause contributes either ordering, return fields, or pricing information.

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 usefully enumerates the metrics returned, so an agent knows what it gets without a follow-up call. Pagination behavior is left to the cursor parameter's schema text, a minor gap for a paged list endpoint.

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% for both parameters, including the '@' handling for handle and the source of the cursor value, so the schema carries the semantic load. The description adds no parameter-level detail beyond what is already documented, which matches the baseline for full schema coverage.

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 names a specific resource (a profile's videos) and adds real scope detail: ordering is 'newest first' and the payload includes plays, likes, comments, shares and saves. It does not distinguish itself from close siblings such as tiktok_collection_videos, tiktok_liked_videos or tiktok_song_videos, so an agent must infer the boundary from the name alone.

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?

There is no explicit when-to-use or when-not-to-use guidance and no named alternative. An agent looking for a user's videos versus a collection, liked list, or song's videos gets no routing signal from this text.

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