amazon ads get campaigns

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

Annotations already declare readOnly/idempotent/non-destructive, and the description adds behaviour that annotations do not: default inclusion of PAUSED and ARCHIVED, page-vs-total semantics, and the fact that results are configuration rather than metrics. It stops short of describing error or auth behaviour, so not a 5.

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, each carrying distinct information: scope, pagination rule, and the config-vs-metrics caveat. Front-loaded with the resource and zero filler.

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 schema, an output schema, and read-only annotations, the description covers the remaining agent-relevant gaps (pagination, default states, entity type). It is nearly complete; only error/permission context is absent, which is minor here.

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 structured form. The description reinforces the nextToken continuation rule but adds no syntax or format detail 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?

Names a specific verb and resource ('Read one page of Amazon Sponsored Products campaigns') and implicitly distinguishes itself from the SB/SD campaign siblings by pinning the ad product. It also rules out a plausible misread by stating these are configuration records, not performance metrics.

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 concrete usage context: pause/archive states are included by default, and the agent must follow nextToken until it is absent because one page is not an account total. It does not explicitly name alternatives like amazon_ads_get_sb_campaigns, but the sibling names make the product split self-evident.

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