Launch a TikTok campaign

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

Annotations only supply readOnlyHint=false, so the description carries the rest, and it delivers genuinely useful behavior: the campaign 'starts paused' and requires a preview confirmation before going live. That is exactly the kind of non-obvious side effect an agent could otherwise assume away. It stops short of describing error behavior or post-launch state transitions.

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 short sentences, the essential action first, with the paused-start and preview caveat immediately after. Nothing is redundant and nothing is buried.

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?

For a zero-parameter launch action with no output schema, the description covers the key state fact (starts paused) and the gating step (confirm preview). It is thin on how the video argument is supplied and what the tool returns on success, but the annotations and narrow scope limit how much more is needed.

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?

The schema declares zero properties (additionalProperties: true), so the baseline is 4. The description mentions 'your video' as the input but does not name or describe the parameter that carries it, leaving the agent to infer where the video reference comes from.

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 ('Launch a TikTok campaign') and names the required asset ('with your video'), which distinguishes it from launch_meta_ad, launch_search_campaign, and launch_pmax_campaign by platform. It never names those siblings explicitly, so differentiation relies on the agent inferring from the platform word.

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?

Usage is implied rather than prescribed: the phrase 'with your video' signals the prerequisite, and the preview-confirmation step hints at the intended workflow. There is no statement of when this tool is preferable to launch_campaign or launch_cloned_ad, and no exclusions.

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