create_tiktok_campaign

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

With no annotations provided, the description carries full burden and does well by disclosing key behavioral traits: campaigns are created in DISABLE state, requires Pro plan or higher ($69/mo), and mentions TikTok minimum budget constraint. It doesn't cover error handling or response format, but provides substantial operational context.

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 perfectly front-loaded with the core functionality in the first clause, followed by important operational details. Every sentence adds critical information with zero waste - state, activation method, budget constraint, and plan requirement.

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 creation tool with no annotations and no output schema, the description provides excellent context about the creation state, activation requirements, budget constraints, and plan prerequisites. It could mention what happens on success/failure or return format, but covers most critical operational aspects well.

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 schema already documents all 7 parameters thoroughly. The description adds minimal parameter-specific information beyond reinforcing the TikTok minimum budget constraint. Baseline 3 is appropriate when schema does the heavy lifting.

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 creates a complete TikTok ad campaign with campaign, ad group with targeting, and ad in one call. It specifies the resource (TikTok ad campaign) and distinguishes from siblings like create_meta_campaign by explicitly mentioning TikTok.

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 context for when to use this tool (creating TikTok campaigns) and mentions the need to call enable_tiktok_campaign to activate. It doesn't explicitly state when not to use it or compare with alternatives like create_meta_campaign, but the TikTok-specific focus provides good guidance.

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