amazon ads get product ads

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, openWorld), but the description adds real context beyond them: results include paused and archived entities by default, a single call is not an account total, and the records are configuration not performance data. It does not mention permission or profile prerequisites, leaving the schema to carry that.

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 with zero filler: scope first, then the pagination rule, then the crucial caveat about totals and record type. Each sentence carries distinct information an agent would otherwise get wrong.

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 a full input schema, an output schema, and rich annotations, the only remaining agent risks are misunderstanding page-vs-total and entity type, both of which the description explicitly addresses. Nothing needed to call it correctly is missing.

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 every parameter (states, accountId, nextToken, maxResults, campaignIds) is already documented in the schema. The description only restates the pagination concept via nextToken and adds no format or constraint detail beyond it, which is the baseline-3 case when the schema does the heavy lifting.

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 one page of Amazon Sponsored Products product ads'), and the 'Sponsored Products' qualifier separates it from amazon_ads_get_sd_product_ads and amazon_ads_get_sb_ads. The closing clause 'configuration records, not performance metrics' further distinguishes it from the report tools 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 clear operational guidance ('Continue with nextToken until absent; one page is not an account total'), which tells the agent how to consume the tool rather than when to pick it. It never names an alternative sibling or an exclusion condition for choosing this over the SD/SB product ad variants, so selection guidance is only implied by the vendor qualifier.

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