direct.hf.update_adgroup_geo

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

No annotations are provided, so the description carries the full burden. It implies a mutation ('set') but does not say whether existing geo targeting is replaced, what apply/dry_run do, or what permissions are required - a significant gap for a write tool with zero structured behavioral coverage.

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 is structurally fine, but at this length against a 9-parameter mutation tool it reads as under-specification rather than genuine conciseness. The 'Human-friendly:' prefix consumes space without adding meaning.

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 9-param, no-annotation, no-output-schema mutation tool, the description omits dry_run/apply semantics, replacement behavior, id resolution, and required identifiers. An agent cannot safely invoke this without opening the schema and guessing.

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 only 22% across 9 params, and the description adds essentially nothing beyond echoing 'RegionIds' (the region_ids param). The meaning of apply, dry_run, campaign_id/name, adgroup_id/name, and their relationships is left entirely undocumented.

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+resource ('set RegionIds for an ad group'), and the 'for an ad group' scope implies the contrast with the sibling set_campaign_geo. However, it never names that sibling or explains what 'RegionIds' targeting means operationally, so differentiation is only implicit.

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?

No when-to-use guidance, no prerequisites, and no mention of the obvious alternative (set_campaign_geo) or of how to discover adgroup ids (find_adgroups). The agent must infer all trigger conditions from the name alone.

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