direct.hf.apply_utm_to_ads

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

With no annotations, the description carries the full behavioral burden and largely ignores it. It never mentions that the schema exposes apply, dry_run, and overwrite flags, so an agent cannot tell whether a call mutates live ads, previews, or whether the run defaults to dry-run.

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 short sentence, front-loaded with the verb and resource, which is structurally efficient but under-specified rather than concise. The trailing '(utm_mode=auto)' fragment refers to a non-existent parameter and clutters rather than clarifies.

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 mutation tool with no annotations and no output schema, the description omits the safety-relevant semantics of apply, dry_run, and overwrite, and never states what is modified or returned. Too thin for the complexity it wraps.

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 25% (two of eight params documented), so the description should compensate but does not. Worse, it introduces 'utm_mode=auto', which is not an input parameter at all, adding confusion rather than semantics for utm_template, campaign_id, apply, dry_run, or overwrite.

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 and resource: apply a UTM template to ads within a campaign. An agent can tell what it does, but it does not distinguish itself from siblings like direct.hf.set_campaign_utm_template or direct.hf.set_adgroup_tracking_params that operate on adjacent objects.

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, when-not-to-use, or prerequisite guidance. 'Human-friendly' hints it is a wrapper over a raw Direct operation but gives no condition under which an agent should prefer it over set_campaign_utm_template or set_campaign_tracking_params.

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