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

Annotations already declare destructiveHint=true and non-idempotent, and the description is consistent with that via the DELETE option. It adds genuinely useful context beyond annotations: the confirm=false dry-run versus confirm=true apply two-step workflow, which is not captured in the structured hints.

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 terse sentences, each carrying distinct information, with the core action front-loaded and parameter details following. No filler or redundancy.

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 destructive multi-target status mutation, the description covers the action, the ID format, the operation enum, and the safety-affirming preview flow, while an output schema exists so return values need not be described. It falls short only on sibling routing and advertiser_id.

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?

With 0% schema description coverage, the description carries the load well: it explains adgroup_ids is comma-separated, enumerates operation as ENABLE|DISABLE|DELETE, and defines confirm semantics. Only advertiser_id is left undocumented, which is a minor gap given how standard it is.

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 specific verbs (enable/pause/delete) and a specific resource (TikTok ad groups), scoping it clearly against siblings like update_tiktok_ad_status and update_tiktok_campaign_status. It does not explicitly name the general-purpose sibling update_tiktok_adgroup it should be contrasted with, keeping it just below a 5.

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 explains the confirm preview/apply mechanic, which is operational guidance, but gives no explicit when-to-use versus alternatives (e.g., update_tiktok_adgroup for non-status edits). The scope is implied by 'status' and 'operation' rather than stated as a routing rule.

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