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

Annotations already declare destructiveHint=true, idempotentHint=false and openWorldHint=true, so the safety profile is covered. The description adds meaningful context beyond them: that DELETE is irreversible, that confirm=false performs a dry-run preview before applying, and that multiple campaigns are batched in one call.

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?

Four short clauses, action and required parameters front-loaded, no filler. The telegraphic 'param: meaning' style is efficient though slightly terse rather than flowing prose.

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?

An output schema exists so return values need not be described. For a destructive multi-target mutation, the preview/apply mechanism and batching are disclosed, which is the key missing piece in most such tools. Only advertiser_id semantics remain unaddressed.

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 carries the full burden and largely does: it documents the comma-separated format of campaign_ids, the ENABLE/DISABLE/DELETE values for operation, and the preview semantics of confirm. Only advertiser_id is left unexplained, which is the sole gap.

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 (enable/pause/delete) and resource (TikTok campaigns), with the three operations enumerated. It is clearly distinguishable from update_tiktok_campaign (settings edit) and update_tiktok_campaign_budget, though it never names those siblings explicitly.

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 confirm=false/true preview-versus-apply split gives real invocation guidance, which is better than most. However there is no guidance on when to prefer this over update_tiktok_campaign or update_tiktok_campaign_budget, and no stated prerequisites (e.g. permissions or campaign state required).

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