direct.hf.ensure_assets_for_campaign

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 implies a mutation ('ensure', 'attach') but does not disclose permissions, idempotency, overwrite semantics, dry-run/apply behavior, or whether missing assets are created. This leaves critical safety and side-effect context undocumented.

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 description is a single front-loaded sentence with little waste, though the 'Human-friendly:' prefix adds no operational value. For a 9-parameter mutation tool, it is concise to the point of under-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?

Given 9 parameters, no required fields, no annotations, no output schema, and only 22% schema description coverage, the description is not complete enough for reliable invocation. It omits the meaning of key flags and does not explain how the composite ensure/attach behavior interacts with existing assets.

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 22%, so the description must compensate, but it adds almost no parameter meaning. It names sitelinks, callouts, and campaign, yet critical controls like apply, dry_run, overwrite, campaign_id vs campaign_name, and account_id are not explained beyond what little the schema provides.

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 states a specific composite action: ensure sitelinks and callouts exist and attach them to ads in a campaign. It is clear enough to distinguish from single-purpose siblings like attach_sitelinks_to_ads or attach_callouts_to_ads, though it does not explicitly route the agent among them.

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 explicit guidance on when to use this composite tool versus the separate attach/create siblings. The implied use case is 'when you want both sitelinks and callouts ensured and attached', but the description does not state prerequisites, alternatives, or exclusions.

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