snapchat get media

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint, so the safety profile is covered. The description adds only that pagination is via next_cursor; it says nothing about return volume, ordering, or what 'retaining full native configuration' actually means in output terms.

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 first sentence is front-loaded and efficient. The second sentence ('An ad squad is an ad group/ad set') is off-topic for a media-listing tool and does not earn its place, dragging an otherwise tight definition down.

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 a full schema, an output schema, and rich annotations, most structured burden is already carried, so the description only needs to disambiguate. It does not: the boundary between this and the creatives/media-status tools is left entirely implicit, which is the main remaining gap.

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%, with limit, cursor, and adAccountId each documented in the schema itself. The description's mention of next_cursor simply echoes the cursor parameter, adding no syntax or constraint detail beyond what the schema supplies, 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?

The description gives a specific verb and resource: 'List Snapchat media in the selected account,' and names the pagination affordance (next_cursor). It never distinguishes this from closely-named siblings like snapchat_get_creatives, snapchat_list_ad_creatives, or snapchat_get_media_status, so an agent cannot tell them apart from the text alone.

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?

There is no when-to-use guidance and no exclusion criteria — nothing says when to prefer this over snapchat_get_creatives or snapchat_get_media_status. The trailing sentence about ad squads being ad groups/ad sets is unrelated to this tool and offers no routing value.

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