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

With no annotations, the description carries the full burden and does cover auth ('Authorization: Bearer <api_key>'), cost ('1 credit(s) per request') and public-only scope, which are genuinely useful. It stops short of describing pagination behavior, result limits, or what the response looks like, which matters for a cursor-driven list endpoint. Solid but incomplete for an unannotated tool.

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 purpose is front-loaded in a single clean sentence, which is good. But the 'Platform=tiktok resource=profile/videos' clause is pure redundancy with the tool name, and there is a stray double period ('username..'). Still short overall, but a sentence does not earn its place.

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?

This is a simple read tool with two fully documented parameters and no output schema, so the bar is low. Auth and credit cost are disclosed, but return shape and pagination flow are not, and for a cursor-based listing the agent is left to infer how to page. Adequate, not complete.

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 both 'username' and 'cursor' are already documented in the schema, including the 'without @' note. The description adds no format or semantics beyond that, so the baseline 3 applies. The cost line is unrelated to parameters.

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 first sentence states a specific verb and resource: 'Fetch recent public videos for a username'. That is enough to separate it from siblings like tiktok_profile/info or tiktok_videos/info, which return a single video or profile data. The trailing 'Platform=tiktok resource=profile/videos' merely restates the tool name and adds nothing.

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?

Usage is only implied: an agent can infer this is the tool for listing a user's videos. The description never names an alternative such as tiktok_videos/info or tiktok_hashtag_videos, nor does it state when not to use it. It does at least establish the 'public' and 'recent' scope, which rules out private or historical fetches.

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