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 by structured data. The description adds genuinely new behavior: a confirm=false dry-run preview vs confirm=true apply, which is not expressible in the annotations and is critical for a destructive tool.

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 telegraphic clauses, front-loaded with the action and operation set, then the two argument-format details. No filler and nothing repeated from the schema.

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 no explanation, and the dry-run flag plus the mutation semantics give an agent enough to call this safely. The only gap is that permanence of DELETE (irreversible vs. a recoverable paused state) is never stated.

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 it does so well for three of four params: ad_ids format (comma-separated), the operation enum values (absent from the schema, which declares no enum), and confirm's preview/apply semantics. Only advertiser_id is left unexplained, though its meaning is self-evident.

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+resource (enable/pause/delete TikTok ads) and enumerates the three operations, so an agent knows exactly what state transitions are possible. It does not explicitly distinguish itself from near-siblings like update_tiktok_ad, update_ad_status, or update_tiktok_adgroup_status, so the reader must infer the 1:1 mapping from the name.

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?

There is no statement of when to use this tool versus the generic update_ad_status or the field-editing update_tiktok_ad/update_tiktok_adgroup_status siblings, and no prerequisites (e.g. ads must be in a state that permits pausing). Usage is only implied by the operation enum.

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