amazon ads list profiles

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

Adds real behavioral detail beyond the annotations: profiles outside the allowlist are never returned or counted, and configured-but-absent IDs surface in missingProfileIds. Annotations already establish read-only/idempotent safety, so this is meaningful extra context, though it says nothing about pagination or failure modes for unreachable regions.

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 compact sentences, front-loaded with what is listed, then the allowlist constraint, then the edge-case output field. No 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 an output schema present and no parameters, the description covers what is returned (marketplace, account type, currency, timezone) and explains the one non-obvious output field, missingProfileIds. Nothing needed to invoke it correctly is absent.

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?

Zero parameters, so the baseline is 4; the description still adds value by naming the two configuration sources (AMAZON_ADS_PROFILE_IDS and AMAZON_ADS_REGION) that implicitly drive the result set.

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 (List) and resource (advertising profiles), plus scope qualifiers: only profiles in AMAZON_ADS_PROFILE_IDS reachable in AMAZON_ADS_REGION. This clearly separates it from the singular sibling amazon_ads_get_profile and from the many get_* campaign/ad-group tools.

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?

The description implies this is the enumeration step constrained by an allowlist, but never explicitly says when to call it versus amazon_ads_get_profile or which siblings depend on its output. The scoping rule is clear; the selection guidance is left implicit.

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