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

Annotations already cover safety (readOnlyHint=true, destructiveHint=false, openWorldHint=true), so the description's added value is the operational caveat that TikTok cover URLs expire and a fresh one should be passed, plus the chaining guidance. That is genuinely useful behavioral context beyond the annotations, though no detail is given on rate limits, batching behavior, or failure modes on unreadable URLs.

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?

Front-loaded with the when-to-use condition and efficient overall, with the source tools and TikTok caveat placed usefully. However, the opening sentence and the later 'Use for comprehensive ad analysis' restate the same usage trigger, which is a small amount of wasted text.

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?

With an output schema present, the description need not explain return values, and it is otherwise sufficient for a 6-parameter, chunked workflow tool. It could go further on how multiple media_urls are handled in one call, but nothing essential for correct invocation is missing.

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 all six parameters including media_urls and total_impressions are already documented in the schema, and the baseline is 3. The description only adds provenance context (which tools produce valid media_url values) and the TikTok URL freshness caveat, which is mildly useful but mostly redundant with the schema.

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?

Specific verb+resource ('analyze ad images') plus an explicit enumeration of what is extracted (text, colors, people, brand elements, composition), which is image-specific and implicitly separates it from the analyze_ad_video sibling. An agent can tell what this tool produces without opening the 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?

States when to use it ('when you want to understand the visual elements in ad images') and names the upstream sources (get_meta_ads, get_google_ads, get_tiktok_ad_details) plus the follow-up tool (get_competitive_brief). It does not explicitly state when NOT to use it, e.g. directing video content to analyze_ad_video, so it falls short of a full 5.

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