pause_tiktok_campaign

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

With no annotations provided, the description carries the full burden. It discloses key behavioral traits: the action is a mutation (pause), it preserves settings, it stops spending, and it has a plan requirement. However, it doesn't mention potential side effects like timing delays or error conditions.

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 front-loaded with the core purpose, followed by additional context in a structured way. Every sentence adds value: the first states the action and outcome, the second provides behavioral context and alternative, and the third specifies requirements.

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 mutation tool with no annotations and no output schema, the description does well by covering purpose, usage, and key behaviors. However, it lacks details on return values or error handling, which would be helpful given the complexity of pausing a campaign.

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 the single parameter 'campaign_id'. The description doesn't add any parameter-specific details beyond what the schema provides, such as format examples or constraints, meeting the baseline for high coverage.

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 specific action ('pause') on a specific resource ('running TikTok campaign') with the explicit outcome ('stop all spending'). It distinguishes from the sibling tool 'enable_tiktok_campaign' by mentioning it as the alternative for resuming.

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?

It provides explicit guidance on when to use this tool (to pause a running campaign and stop spending) and when to use an alternative (use enable_tiktok_campaign to resume). It also specifies prerequisites (requires Pro plan or higher).

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