snapchat get ads

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

Annotations already declare readOnly, idempotent, non-destructive, open-world, so the safety profile is covered. The description adds that results are paginated via next_cursor and that entities keep their full native configuration, which is useful context, but it stops short of anything about ordering, page exhaustion, or error behavior on an invalid adAccountId.

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?

Two short sentences, purpose front-loaded, no filler. The terminology sentence is short and does real work by disambiguating ad squad vs ad, though it could have been folded into a routing hint instead.

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 and full schema documentation, the description doesn't need to explain returns or parameters; it covers purpose, scope, and pagination adequately for a simple list tool. The remaining gap is sibling routing among the many snapchat_get_* list tools.

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%: limit bounds, cursor opacity, and the adAccountId UUID-vs-organization-ID warning are all documented in the schema. The description only echoes the next_cursor concept and adds no new parameter meaning, so the 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 and resource ("List Snapchat ads") plus scope ("in the selected account"), which separates it from siblings like snapchat_get_adsquads and snapchat_get_creatives. The closing line defining an ad squad as an ad group/ad set reinforces the ads-vs-adsquads boundary, though it never names the sibling tool to use for ad groups.

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 by "List Snapchat ads in the selected account" — an agent can infer this is the read path for ads, but the description gives no explicit when-to-use, when-not-to-use, or alternative (e.g., use snapchat_get_adsquads for the parent ad groups) despite 20 sibling tools.

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