download_tiktok_video

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

No annotations are provided, so the description carries the full burden. It discloses return values (download links, title, author, stats) but omits behavioral traits like rate limits, required authentication, or whether the download is permanent. Moderate transparency but missing operational details.

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?

A single sentence that packs essential information: action, output specifics, and result format. No filler, logically structured, and front-loaded with the core action.

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?

Without an output schema, the description compensates by listing return values (links, title, author, stats). This is sufficient for a simple download tool with one input. However, missing details like file quality or size would improve completeness for production use.

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% with a single parameter. The description adds an example URL pattern in the schema, matching the baseline expectation. No additional parameter meaning beyond what the schema provides, leading to a midpoint score.

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 tool downloads a TikTok video without watermark, distinguishing it from siblings like extract_tiktok_audio_mp3 or calculate_tiktok_engagement_rate. The verb 'download' and resource 'TikTok video' are specific and unambiguous.

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?

No guidance on when to use this tool versus alternatives. For example, it does not mention that extract_tiktok_audio_mp3 is for audio-only downloads or that other tools cover analytics. The agent must infer usage context from sibling names alone.

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