direct.hf.create_adgroup_simple

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

No annotations are provided, so the description carries the full behavioral burden for what is clearly a write operation. It only implies "create"; it says nothing about the dry_run/apply flags, reversibility, required auth (Direct Client-Login), or what occurs on partial input, leaving the mutation's side effects undisclosed.

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, and "Human-friendly" is the only differentiation cue so it earns its place. The trade-off is that conciseness here shades into under-specification rather than tight completeness.

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 an 8-parameter write tool with no annotations and no output schema, the description is far too thin. It conveys basic purpose but omits required inputs, the safe dry_run/apply pattern, and any return or failure behavior an agent would need to call it correctly.

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 only 25% across 8 parameters (name, apply, dry_run, region_ids, campaign_id, campaign_name are undocumented), and the description adds no field-level meaning. The phrase "under a campaign" faintly implies campaign_id/campaign_name linkage despite both being marked optional, but this is too implicit to compensate for the coverage gap.

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 gives a clear verb and resource ("create ... ad group") plus scope ("under a campaign"). However, "simple" and "Human-friendly" are vague qualifiers and do not explicitly distinguish this tool from the raw sibling direct.create_adgroups or from direct.hf.find_adgroups, so the agent must infer the difference from the tool name rather than the description.

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 when-to-use guidance, no statement of when to prefer this over direct.create_adgroups, and no named alternatives or preconditions. The description never mentions the apply/dry_run workflow or what happens without a campaign identifier, leaving selection and sequencing entirely to inference.

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