Draft Reddit ad group changes

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

Beyond the annotations, it discloses replacement semantics for targeting lists (omitted keys preserved), budget/bid validation limits, the schedule block format with inclusive end_hour and viewer-local timezone, and location placement values. This is exactly the non-obvious behavior an agent needs to call it safely.

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 front-loaded with a one-line summary and then organizes details by theme; every sentence adds operational information. It is dense but not padded.

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 a 23-parameter tool, it covers the main traps (validation, replace semantics, schedule format, timezone, placements) and an output schema exists to describe returns. It could be more explicit that the operation is a draft requiring confirm_and_apply, and it doesn't enumerate all parameters, but the essentials are covered.

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?

With 0% schema coverage, the description compensates by explaining the tricky parameters (schedule, budget pair, locations) and the shared REPLACE rule for targeting arrays. Some remaining parameters (gender, platforms, bid_strategy, expand_targeting) are only covered generically as targeting, so it is not a complete map, but the critical semantics are present.

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 first sentence uses a specific verb (draft changes) and resource (Reddit ad group) and enumerates the affected dimensions (budget, bid, run dates, schedule, targeting), which separates it from siblings like update_reddit_campaign or update_reddit_ad. The title reinforces the drafting nature, so an agent can identify its job immediately.

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 establishes when this tool is appropriate by framing it as drafting changes and pointing to search_reddit_targeting for id/name lookup, and implicitly to confirm_and_apply for applying drafts. It does not explicitly state exclusions or contrast with draft_reddit_ad_group, so a small inference gap remains.

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