tiktok_upload_draft

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

Annotations already flag the write, non-idempotent, open-world nature, and the description adds real behavior: the endpoint accepts source_info only, the video lands in the inbox and is not published, and #Shorts is stripped from the caption. It omits practical constraints such as file size or duration limits, keeping it below a 5.

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?

Two dense sentences, front-loaded with the action and endpoint, with no filler. The second sentence is somewhat run-on and packs caption-building, #Shorts stripping, and the AI-label reminder together.

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?

With no output schema, the description correctly explains the return value (a ready-to-paste caption plus an AI-generated content label reminder) and the manual follow-up step. It leaves out media constraints and failure behavior for an uploaded file, which would complete the picture.

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 schema already documents all four parameters, establishing a baseline of 3. The description adds a precedence rule (spec_path vs title/hashtags override) that is only partly reflected in the schema wording, but nothing further about formats or validation.

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: upload a local MP4/MOV file as an Inbox Draft to the creator's TikTok app, and names the exact API endpoint used. It is immediately distinguishable from the yt_* siblings and from a direct-publish tool.

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?

Makes clear this creates a draft the creator finishes manually in the mobile app rather than a published post, which is the key routing fact. It never explicitly names an alternative tool or states when not to use it, so it falls short of full 5-level guidance.

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