tiktok_create_bundle

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 that the tool does not upload but prepares a local bundle, describes output files (images/, caption.txt, manifest.json, README.txt, ZIP), and specifies constraints (2-35 images, 1-2200 chars, max 30 hashtags). It lacks mention of side effects like overwriting existing bundles, but creation tools are generally non-destructive.

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 well-structured with a clear lead sentence, bullet-like list of output files, and separate line for each argument. It is somewhat long but every sentence adds value. Could be slightly more concise by grouping some lines, but still efficient.

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 7 parameters, no annotations, and presence of output schema, the description is thorough. It explains the entire workflow from input to output, the rationale for manual transfer, and provides constraints for each parameter. The return format (JSON with ok, bundle_id, zip_path) is mentioned, complementing the output schema.

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 0%, so the description adds significant value beyond the schema. It explains each parameter: images_dir (absolute path, 2-35 PNG/JPG), caption (1-2200 chars), hashtags (optional list, max 30, no '#'), series_slug (lowercase, no spaces), part_slug (optional), bundles_dir (override), make_zip (boolean, default true). It provides constraints and defaults not evident in the schema titles.

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 tool name 'tiktok_create_bundle' clearly indicates a creation action. The description explicitly states it 'bundle[s] a folder of images + caption for TikTok mobile upload' and distinguishes from siblings (delete, get, list) by focusing on creation of a bundle for manual transfer.

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 provides clear usage context: 'Photo carousel can only be uploaded from TikTok mobile app (not web)' and 'User then copies the ZIP/folder to their phone and uploads manually.' It does not explicitly state when not to use, but the context of manual upload implies it is not for automated posting.

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