amazon ads get sd ad groups

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

Annotations already declare read-only, idempotent, non-destructive, open-world behavior. The description adds meaningful context beyond them: Display eligibility, offset-based pagination rather than cursors, conservative partial-page marking, and a clarification that records are not performance metrics.

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 short, front-loaded, and largely waste-free. The final sentence about native media references is useful but slightly tangential for an ad group listing tool.

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 rich annotations, full schema coverage, and an output schema, the description supplies the key missing behavioral context: eligibility, pagination quirks, and the non-performance nature of the records. It is complete enough for an agent to invoke the tool 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 coverage is 100%, so the schema already documents accountId, count, and startIndex. The description adds pagination-related nuance about startIndex and partial pages, but does not add parameter meaning beyond what the schema provides for accountId or count.

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 ad groups.' The 'Sponsored Display' qualifier distinguishes it from the sibling non-SD ad group tool, but it does not explicitly name alternatives or contrast with them.

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 a prerequisite ('Requires Display eligibility') and pagination guidance, but does not say when to use this tool versus siblings such as amazon_ads_get_ad_groups or amazon_ads_get_sd_campaigns. Usage is implied by the SD scope rather than explicitly directed.

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