amazon ads list creative assets

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

Annotations already declare this as a read-only, idempotent, non-destructive, open-world operation. The description adds useful behavior beyond that: pagination via nextToken with the same filters, returned download/playback URLs and moderation metadata, and the caveat that uploaded assets do not prove campaign delivery.

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 description is front-loaded and dense: the first sentence establishes the search scope and return content, followed by pagination, a caveat, and a sibling alternative. Every sentence contributes useful selection or invocation information.

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?

Given rich annotations, full schema descriptions, and an output schema, the description provides enough additional context to call the tool correctly. It covers pagination, filter reuse, asset types, caveats, and the key sibling alternative for Sponsored Products images.

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 the parameters are already well documented. The description reinforces that nextToken must be used with the same filters, but otherwise adds little parameter-level meaning beyond what the schema already provides.

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 uses a specific verb and resource: "Search the Amazon creative asset library" and enumerates the asset kinds and returned details. It also distinguishes this listing tool from amazon_ads_get_product_metadata for Sponsored Products images, so an agent can identify its role without opening the schema.

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?

It states the search context, explains one-page pagination with nextToken, and explicitly routes Sponsored Products images to amazon_ads_get_product_metadata instead. The caveat that uploaded assets are not proof of campaign use or delivery also clarifies the tool's evidential limits.

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