Reddit ads

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

Annotations already establish readOnlyHint, so no safety contradiction exists. The description adds real behavioral detail beyond annotations: include_copy triggers 'one request per distinct post' and returned insights flag rejected/pending ads.

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 compact, front-loaded with the core listing purpose, and each sentence adds meaningful behavior. There is no filler or repetition of schema defaults.

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 a rich output schema, the description covers the main return fields, the optional include_copy behavior, and status insights. The only notable gap is the undocumented filter parameters and absence of explicit sibling routing.

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 explains include_copy in detail, but ad_account_id, campaign_id, and ad_group_id receive no semantic explanation or filtering behavior.

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 uses a specific verb and resource: 'List Reddit ads' with concrete fields like status, rejection_reason, post and click URL. This clearly separates it from sibling tools such as get_reddit_campaigns and get_reddit_ad_groups.

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 gives useful context for include_copy ('creative can be reviewed without opening Reddit') and for interpreting REJECTED and PENDING_APPROVAL statuses. However, it does not explicitly mention when to prefer this tool over alternatives or when not to use it.

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