tiktok_download_user_media

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

No annotations provided, so the description carries full burden. It clearly states the output format ('organized date folders (YYYY-MM-DD_<id>)', 'post.json', 'account_summary.json') and that it handles photos and HD MP4 videos. It does not mention rate limits or authentication, but as a download tool the behavior is reasonably transparent for agent decision-making.

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 one sentence that packs key information: what is downloaded (photos and videos), how it is organized (date folders), metadata files included, and account summary. It is concise and front-loaded, though additional details about the format could be considered but would add length.

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 tool's moderate complexity (4 parameters, no output schema, no annotations), the description is fairly complete. It explains the output structure and file naming, which is critical for an agent to understand what will be created. Missing details on rate limits or required permissions, but for a download tool the core behavior is covered.

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 baseline is 3. The description adds value by explaining the output structure and overall purpose, but does not add specific parameter-level details beyond what the schema already provides. However, the enum for media_type and defaults for max and output_dir are self-explanatory. Scores 4 because the description context complements the schema well.

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 uses specific verbs ('download') and resources ('media from a TikTok account') and clearly distinguishes from siblings like tiktok_extract_post or tiktok_get_user_posts by mentioning 'organized date folders', 'post.json', and 'account_summary.json'. It differentiates itself well.

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 when to use this tool (to download all media from a TikTok account) but provides no explicit guidance on when not to use it or alternatives. Given sibling tools like tiktok_get_user_posts or tiktok_download_post exist, it would benefit from stating when to prefer this over fetching or downloading a single post.

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