snapchat list ad creatives

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

Annotations already cover safety (readOnly, idempotent, non-destructive, open-world), so the description earns credit for adding real behavior: media URLs are short-lived Snap-hosted links that the server does not download, incomplete formats/media are surfaced rather than hidden, and no performance metrics are derived. These are exactly the surprises an agent needs warned about.

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 sentences, purpose front-loaded, each subsequent sentence contributing a distinct operational caveat (incomplete reporting, no performance, URL lifetime). No filler or restatement of the tool name.

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?

Output schema exists so return shape need not be described, annotations cover safety, and the description still adds the important caveats about short-lived URLs and missing coverage. Only the routing to sibling creative/media tools is left unstated.

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% and the description adds nothing parameter-specific — the 'omit adIds resolves first ads of the account' behavior is already documented in the schema. Baseline 3 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 ('Resolve') and a specific resource set ('ad-linked Snapchat images/videos, Story children and Collection tiles') and names the payload fields returned. The 'ad-linked' and 'resolve media' framing implicitly separates it from snapchat_get_creatives and snapchat_get_media, but no sibling is named 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?

Usage is only implied: 'No performance is inferred' scopes it away from insights/reporting tools and 'Incomplete formats/media are reported' hints at its diagnostic role. There is no explicit when-to-use / when-not-to-use, and neither snapchat_get_creatives nor snapchat_get_media is mentioned as an alternative.

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