snapchat get adsquads

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

Annotations already declare readOnly, idempotent and non-destructive, so the safety profile is covered. The description still adds real context: results paginate via next_cursor and are returned with 'full native configuration', telling the agent to expect raw upstream-shaped payloads rather than a normalized projection.

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 tight sentences, front-loaded with the action and scope; the second sentence exists solely to define the business term 'adsquad'. Nothing is wasted and nothing essential is buried.

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, return-value detail needn't be in the description, and read-only behavior is covered by annotations. The description supplies the entity definition and pagination model, which is sufficient for correct invocation; only sibling routing is left open.

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 all three parameters are documented inline, including cursor provenance and the adAccountId UUID constraint. The description only echoes cursor/account scoping, adding no format or edge-case detail beyond the schema, so 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 adsquads') scoped to 'the selected account', and disambiguates the terminology by equating an ad squad with an ad group/ad set. It does not explicitly distinguish itself from sibling list tools like snapchat_get_campaigns or snapchat_get_ads, leaving hierarchy to inference.

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 implied by 'in the selected account' and by the pagination note, but there is no explicit when-to-use/when-not or named alternative among the many sibling get_* list tools. An agent can infer the context but must decide on its own between this and snapchat_get_campaigns/snapchat_get_ads.

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