reddit list ad creatives

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

Annotations already declare readOnly/idempotent/non-destructive, and the description adds meaningful behavior beyond them: media URLs are returned but never downloaded, and a video cover does not represent its motion/audio. That is exactly the kind of non-obvious output semantics an agent needs. It stops short of covering pagination behavior or the per-call 20-ad resolution cap (left to the schema).

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, front-loaded with the resource and followed by the two operational caveats; nothing is wasted. Minor deduction for the vague opener 'with explicit coverage', which reads as internal jargon rather than information.

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, full parameter coverage and read-only annotations, the description only needs to carry the non-obvious semantics, and it does (URLs not downloaded, cover vs full media). The remaining gap is not naming the sibling tool that overlaps with this one.

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 adIds, limit, cursor and adAccountId are fully documented in the schema, including the 'at most 20 resolved per call' cap. The description adds no parameter-level meaning, so 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 ('Resolve') and resource ('ad-linked image/video/carousel assets'), which an agent can distinguish from the list/get siblings reasonably well. However it never mentions the near-neighbor reddit_get_creative_assets, and 'resolve ... with explicit coverage' is jargon that partly obscures what a call actually returns.

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?

Usage is only implied: 'use full media when available' tells the agent to prefer full motion/audio media over a cover, but there is no explicit when-to-use statement or routing against reddit_get_creative_assets, reddit_get_ads, or reddit_get_ad for the same assets. An agent can infer the context but not the alternatives.

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