reddit get ad groups

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description adds value beyond that by disclosing the pagination contract: an opaque cursor with no automatic continuation, which is precisely the kind of behavior an agent needs to plan multi-page reads.

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?

Two sentences, both earning their place: the first defines scope and payload, the second defines pagination behavior. Front-loaded with no filler or restatement of the title.

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 low-complexity read/list tool with full schema coverage, full annotations and an output schema, the description covers the one non-obvious behavioral nuance (manual pagination). It stops short of routing the agent away from the singular get_ad_group sibling, which is the only remaining gap.

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% — limit, cursor and adAccountId are all documented in the schema, including the a2_ prefix and the REDDIT_ADS_ACCOUNT_IDS hint. The description restates the cursor being opaque but adds no format or constraint detail beyond what the schema supplies, 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 and resource ("Read Reddit ad groups") and names the returned content (native configuration, configured/effective status). It does not explicitly distinguish itself from the singular sibling reddit_get_ad_group, but the plural resource plus list semantics make the intent clear.

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 sentence about pagination ("every further page needs an explicit call") is a real usage instruction telling the agent it must loop manually rather than rely on auto-pagination. However, there is no guidance on when to pick this over reddit_get_ad_group or reddit_get_campaigns, so the sibling-selection guidance is only implied.

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