list_tiktok_videos

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

The annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description adds useful auth-scope context by saying the videos belong to the authenticated user, but it does not explain pagination behavior, rate limits, or authentication requirements beyond that phrase.

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 a single front-loaded sentence with no wasted words. It immediately states the core action and target resource.

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 simple list tool with rich annotations and partial schema descriptions, the description is minimally adequate. However, it leaves out pagination context, authentication requirements, and any indication of what the returned video list contains, which matters because there is no output schema.

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?

The schema describes 2 of 3 parameters, including cursor and max_count, so parameter documentation is mostly present. The description's phrase 'authenticated TikTok user' indirectly signals the access_token parameter, but it does not add syntax or behavior details beyond the schema.

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 states a specific verb and resource: list videos for the authenticated TikTok user. It is clear what the tool does, but it does not explicitly distinguish itself from sibling tools such as get_tiktok_video or get_tiktok_user.

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 this is for listing the authenticated user's own videos, but it gives no explicit when-to-use guidance, no exclusions, and no alternative tools to consider. An agent must infer the usage context from the phrase 'authenticated TikTok user.'

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