Reddit ad groups

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered. The description adds meaningful operational context: Reddit requires conversion_pixel_id on every ad group preliminary, and insights will flag ad groups missing one. That goes beyond the annotations and informs the caller about validation behavior.

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 two crisp sentences with no filler. The primary action and returned fields are front-loaded, and the important Reddit pixel requirement occupies its own short sentence. Every sentence earns its place.

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?

For a read-only list tool with only two optional parameters and an output schema, the description covers the main purpose, returned field categories, optional campaign scoping, and a key platform requirement. The only notable gap is the unexplained ad_account_id parameter, but the overall context is sufficient for basic correct use.

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 0%, so the description must compensate for parameter meaning. It clarifies that campaign_id is optional and filters by campaign, but it does not explain ad_account_id, its relationship to campaign_id, or how the default empty values behave. One of two parameters is left undocumented.

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 starts with a specific verb ('List') and a specific resource ('Reddit ad groups'), and enumerates the fields returned (budget, bid, pixel, weekly schedule, targeting summary). This clearly distinguishes it from siblings like get_reddit_ads, get_reddit_campaigns, and get_reddit_performance.

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 provides some context by saying the listing is 'optionally per campaign', implying campaign_id can scope the call. However, it does not explicitly say when to prefer this over sibling listing tools or when not to use it, so the usage guidance remains implicit.

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