tiktok_download_post

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

Since no annotations are provided, the description carries full responsibility for behavioral disclosure. It explicitly states the tool downloads content, creates a date-named folder, and saves metadata as post.json, giving the agent a clear operational model. However, it does not mention any potential rate limits, authentication requirements, or handling of unavailable posts.

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, informative sentence that front-loads the action and output specifics. Every element (action, media type, folder naming, metadata) is purposeful, with no superfluous words.

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 no output schema and a simple 2-parameter tool with 100% schema coverage, the description adequately covers input and output structure. It could be enhanced by noting error behavior (e.g., what happens if the URL is invalid) or requiring authentication, but for a straightforward download tool, it is largely 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 the baseline is 3. The description does not add further details about the parameters beyond what the schema already provides (url and output_dir with defaults). It reiterates the output directory usage indirectly but adds no new semantic depth.

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 clearly states the action (download), resource (TikTok post), and key features (unwatermarked HD MP4 video or photo slides). It distinguishes itself from siblings by specifying the output format—a date-named folder with metadata—but it does not directly contrast with sibling tools like tiktok_extract_post or tiktok_download_user_media.

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 downloading individual posts, which differs from siblings that extract data or download user media, but it does not provide explicit when-to-use guidance or exclusion criteria. The agent must infer usage context from sibling names rather than from the description itself.

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