reddit get ad group

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

Annotations already cover read-only, idempotent, open-world, and non-destructive behavior, so the bar is lower. The description adds an ownership-verification behavior, but it does not say what happens on mismatch, whether an error is returned, or what the verification implies for output.

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?

It is a single front-loaded sentence with no filler or redundancy. Every clause contributes to the tool's purpose or its ownership-verification behavior.

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?

Given the simple read operation, complete parameter schema, annotations, and output schema, the description is largely sufficient. Its only meaningful gap is the absence of explicit routing guidance versus the plural list sibling.

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%, and the schema already explains that id must belong to adAccountId and that adAccountId is the a2_... account ID, not the business ID. The description only echoes the 'belongs to' constraint without adding format or syntactic detail.

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 states a specific verb, 'Read', and a specific singular resource, 'one Reddit ad group', which distinguishes it from the plural list sibling reddit_get_ad_groups. It also mentions ownership verification, giving a clear purpose beyond simply fetching.

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 phrase 'Read one' implies the tool is for single-ad-group retrieval and 'verify that it belongs to the ad account' suggests a validation use case. However, it gives no explicit when-to-use guidance, no exclusions, and does not point to reddit_get_ad_groups for multiple records.

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