snapchat get creative elements

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds pagination context (next_cursor) and the claim of retaining "full native configuration," but says nothing about result size, field shape, or error conditions. The ad-squad sentence adds no behavioral insight about this tool.

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?

It is short, but the second sentence defining an ad squad is off-topic for a creative-elements listing tool and consumes 40% of the text with misinformation-adjacent content. The genuinely useful part (pagination retention) is buried after an undefined resource 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?

An output schema exists, so return values need not be explained. However, for a tool in a crowded sibling set with three similarly named creative/media listing tools, the description leaves the agent unable to determine which one returns what.

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%, so all three parameters (limit, cursor, adAccountId) are already documented in the schema; baseline 3 applies. The description's mention of next_cursor only restates what the cursor schema field already says.

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?

"List Snapchat creative elements in the selected account" gives a verb and a resource, but "creative elements" is never defined and is not distinguished from the close siblings snapchat_get_creatives and snapchat_list_ad_creatives. The trailing sentence defining an ad squad appears copied from an adsquad tool and muddies what this tool actually returns.

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 statement of when to use this tool versus snapchat_get_creatives, snapchat_list_ad_creatives, or snapchat_get_adsquads, despite those being the obvious decision points. No prerequisites or exclusions are given.

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