List the swipefile

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint=false and destructiveHint=false, so the safety profile is covered. The description adds value beyond that by enumerating the returned fields (since no output schema exists) and noting it is the same board the web app's Swipefile tab shows, though 'Read-only, free' largely repeats the annotations.

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?

Front-loaded with the core purpose and resource, followed by the returned-field list and use cases. It is somewhat dense and the 'Read-only, free' tail is redundant with annotations, but overall each sentence contributes.

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 no output schema, the description compensates by describing the return payload (collections and ad fields). Both optional params are fully documented in the schema, and usage contexts are covered, so an agent has everything needed to call it correctly.

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 both limit and collection are fully documented in the schema and the baseline is 3. The description adds no extra syntax or default semantics for these params beyond what the schema already states.

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 (list) and resource (the workspace's swipefile/saved-ad board), and describes the returned contents in detail (collections, ads/creatives, advertiser, headline, etc.). It clearly distinguishes this read tool from siblings like save_to_swipefile and export_swipefile_deck.

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 concrete when-to-use guidance: answer 'what have we saved?', mine the user's taste before planning an ad, or find a reference to remix. It doesn't explicitly name an alternative sibling (e.g. export_swipefile_deck for exporting), but the usage context is unambiguous.

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