amazon ads get sb ad creatives

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

Annotations already declare readOnly/idempotent/non-destructive, so the description correctly spends its words elsewhere: eligibility gating and the 'no retail scraping' constraint tell the agent this only returns native API data. Pagination behavior is left entirely to the schema fields, but that is a minor gap.

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?

Three short sentences: what it returns, how to resolve IDs, and the eligibility/caveat line. Nothing is repeated from annotations or the schema, and the core purpose leads.

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-value description is unnecessary, and the eligibility and cross-tool resolution notes cover the main decision points. The only thing an agent might still want is a hint about multi-ad scope (one ad per call), which is implied but not stated outright.

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% and every parameter (accountId, adId, nextToken, maxResults) is documented in detail there. The description adds no syntax or format guidance 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?

States a specific verb and resource ('read native Sponsored Brands creative versions for one ad') plus the concrete payload fields returned (headline, ASINs, logo, image/video refs). The 'Sponsored Brands' qualifier cleanly separates it from amazon_ads_get_sd_creatives in the sibling list.

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 an explicit prerequisite ('Requires Brands eligibility') and routes to the correct follow-up tools for IDs (amazon_ads_get_creative_asset, amazon_ads_get_product_metadata). It doesn't explicitly state the negative case (e.g., use the SD creatives tool for Sponsored Display ads), which keeps it short of a 5.

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