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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so safety is covered. The description adds genuinely useful behavior beyond that: batch lookup is supported, results are served from a cache that the server backfills (creative/cover/body), and landing_page is flagged as the reliable brand signal because brand_name is often absent.

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 purpose and inputs are well front-loaded in the first two sentences, but the 'SHOWING THE ADS' block runs long with prescriptive carousel-formatting rules that read as workflow policy rather than tool semantics. It is not padded with fluff, yet roughly half the description is devoted to rules an agent shouldn't need in order to invoke this specific tool.

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 read tool with an output schema and full annotation coverage, the description supplies everything needed: input forms, batch support, field availability, and the downstream routing. Return-value formatting is correctly left to the output schema. It is complete, though the heavy workflow instruction is more than the tool's own scope requires.

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 coverage is 100% and the schema itself documents that ad_id accepts a single ID, a list, or a URL, matching the description's 'single id/URL string or a list for batch lookup'. The description adds little parameter-level detail beyond the schema (the landing_page note concerns output, not input), so the 3 baseline for high coverage applies.

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 ('Get full creative details' for a TikTok ad ID) and enumerates the returned fields (landing page, country targeting, dates, engagement data). It explicitly names the sibling that produces the required input (search_tiktok_ads) and the accepted URL form, so the agent can distinguish it from get_meta_ads/get_google_ad_details without opening a schema.

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?

Gives an explicit trigger ('when you have a TikTok ad ID ... or a library.tiktok.com detail URL'), names the upstream tool that supplies the ID, and specifies supporting/skip conditions for the downstream carousel ('call show_ad_carousel at least once ... Skip it only when there were zero ads'). Routing is unambiguous.

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