direct.hf.set_campaign_geo

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

With no annotations, the description carries the full behavioral burden and it is thin. It does disclose the bulk scope (all ad groups), but says nothing about whether region_ids replaces or merges with existing targeting, what apply/dry_run mean, whether the change is reversible, or what permissions are needed.

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 single sentence is front-loaded and contains no filler, which is good. However, one sentence is undersized for a 7-parameter mutation tool with two control booleans, so the brevity comes at the cost of necessary specification.

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?

No annotations, no output schema, low schema coverage and seven parameters, including the critical apply/dry_run pair, are all left unexplained. An agent cannot safely invoke this tool without guessing at the dry-run semantics and the replacement behavior of region_ids.

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 coverage is 29% and only account_id and direct_client_login are documented, leaving region_ids, campaign_id, campaign_name, apply and dry_run bare. The description only hints that RegionIds maps to region_ids and does not explain the campaign_id vs campaign_name choice or the apply/dry_run booleans.

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 (set), resource (geo/RegionIds) and scope (all ad groups in a campaign), which lets an agent distinguish it from the sibling update_adgroup_geo that operates on a single ad group. The sibling is not named explicitly, so it stops short of a 5.

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?

There is no guidance on when to use this bulk tool versus update_adgroup_geo, no prerequisites, and no explanation of the apply/dry_run workflow that governs whether the change is actually written. Usage is only implied by the scope phrase.

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