snapchat get mobile apps

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 fully covered by structured data. The description adds the useful prerequisite framing (fetch IDs before campaign/audience creation) but says nothing about result scope, e.g. whether all apps for the account are returned or whether unavailable apps are included.

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?

A single front-loaded sentence with the resource first and the usage trigger second. Every clause carries information; nothing is padded or repeated from the title.

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?

For a one-parameter read tool with an output schema and full annotations, the description covers what it does and when to call it. The only residual gap is result scope (ordering/completeness of returned app IDs), which is minor given the output schema likely defines the shape.

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% and the adAccountId parameter is documented with a strong constraint (UUID from SNAPCHAT_ADS_ACCOUNT_IDS, never an organization ID). The description only echoes 'selected ad account', adding no syntax or format detail beyond the schema, 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?

Specific verb (Read) plus specific resource (Snap App IDs) scoped to the selected ad account, which distinguishes it from sibling lookups like snapchat_get_pixels and snapchat_get_segments. No explicit sibling naming, so it stops short of a 5.

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?

Gives clear situational context: call this before creating app promotion campaigns or mobile retargeting audiences. That is a real when-to-use signal, but there are no exclusions or guidance on what to do if the app is absent or how it relates to the other lookup tools.

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