direct.hf.set_campaign_utm_template

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. It says 'apply,' implying mutation, but does not disclose permissions required, whether existing UTM parameters are overwritten, what dry_run or apply=false actually do, or what a successful call returns.

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 short, but the 'Human-friendly:' prefix is vague filler that does not earn its place and leaves the core action under-specified.

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 is far too sparse. It does not explain required inputs, preconditions, side effects, or how to safely use the apply/dry_run/overwrite flags.

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?

There are 8 parameters with only 25% schema description coverage (account_id and direct_client_login). The description adds no meaning for apply, dry_run, overwrite, campaign_id, utm_template, or campaign_name, and 'utm_mode=auto' is not even a parameter in the schema.

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 UTM template to a campaign'), making the core action clear. However, it does not differentiate itself from sibling tools such as direct.hf.set_campaign_tracking_params or direct.hf.apply_utm_to_ads, so an agent cannot tell which UTM-related tool to select from the name and description alone.

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 alternatives or exclusions. 'Human-friendly' and 'utm_mode=auto' do not explain the scenario where this tool is preferred over the many sibling tools that also set tracking or UTM data.

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