list_tiktok_user_videos

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

Goes well beyond the read-only/idempotent annotations by disclosing a hard upstream limitation: at most 10 videos from the embed page with no further pagination. It also flags that include_details causes an additional fetch per video, which carries cost/latency implications. Missing only notes on failure modes or auth.

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?

Three short sentences, each earning its place: purpose first, then the hard cap, then the option tradeoff. No restatement of the tool name or filler.

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 read-only list tool with full schema coverage, the description covers the essential surprises (10-video ceiling, per-video fetch cost). Without an output schema, it could say a word about what each result contains (IDs, URLs, basic stats), but nothing critical is missing.

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%, so the baseline is 3, but the description adds real meaning: it explains that include_details performs one extra fetch per video and caps the effective result count at 10, which the schema only states tersely. The user and timeout parameters are left entirely to 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?

States a specific verb and resource ('List TikTok videos for one user'), and the platform qualifier alone separates it from YouTube-oriented siblings like list_channel_videos and search_youtube. An agent can route correctly 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?

Explicitly rules out a tempting alternative ('TikTok search is not available') and tells the agent when to set include_details ('to also fetch each video page'). It does not name a sibling tool to use for other platforms, but the usage context is otherwise clear.

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