amazon ads get sd creatives

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

Beyond the read-only/idempotent annotations, it discloses eligibility requirements, the pagination model, and that full pages are conservatively marked partial. It also clarifies that records contain native media references and are not performance metrics, which meaningfully sets expectations.

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?

Four tightly written sentences, front-loaded with the tool's purpose. Each sentence adds a distinct and useful fact: eligibility, pagination behavior, and data content.

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 the rich schema and the existence of an output schema, the description covers the key call-context concerns: eligibility, pagination, and data type. It is nearly complete, though it could explicitly route agents away from sibling creative or product-ad tools.

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%, so the schema already documents all four parameters. The description adds useful pagination semantics by stating that pagination uses startIndex rather than a cursor, helping prevent cursor-style pagination attempts.

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 states a specific verb and resource: 'Read one page of Sponsored Display creatives.' It clearly distinguishes this from SD product ads, targets, and generic creative-asset tools by naming the exact resource and scope.

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 gives clear usage context, including the prerequisite 'Requires Display eligibility' and the caveat that records are 'not performance metrics.' It does not explicitly name alternatives such as amazon_ads_list_creative_assets or amazon_ads_get_sd_product_ads, so exclusions are absent.

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