reddit get campaign

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered. The description adds the mildly useful ownership-verification constraint, but doesn't say what happens on a mismatch (empty result vs. error) or note any rate limits, so it adds only modest context beyond the annotations.

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?

A single front-loaded sentence with no filler; the key scope and the ownership constraint come first. It errs slightly toward under-specification rather than bloat, but nothing in it is wasted.

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 present, return values need no explanation, annotations cover the safety profile, and both parameters are fully documented in the schema. The only real gap is failure behavior when the campaign doesn't belong to the ad account, which keeps it from a 5.

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%: both id and adAccountId are already documented, including the a2_ prefix convention and the REDDIT_ADS_ACCOUNT_IDS source. The description only restates the ownership relationship already present in the id field, 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 ('Read') and resource ('one Reddit campaign'), and the singular scope distinguishes it from the plural sibling reddit_get_campaigns. It doesn't explicitly name the sibling, but the singular/plural contrast plus the ownership check is enough for an agent to disambiguate.

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 implies usage by requiring an adAccountId-scoped campaign read, but it never says when to prefer this over reddit_get_campaigns or what to do if the ownership check fails. Usage context is inferable but not stated.

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