direct.hf.set_campaign_strategy_preset

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

No annotations are provided, so the description carries the full disclosure burden and fails: it does not state that this is a write/mutation, what happens to existing campaign settings, whether the change is reversible, or which permissions/accounts are needed. Critically, it never surfaces the purpose of the `apply` and `dry_run` flags, which are the most behaviorally significant fields in the schema.

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 wastes no words, but its brevity here reflects under-specification rather than efficiency — no actionable detail is packed in.

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?

A 7-parameter mutation tool with no annotations, no output schema, low schema coverage, and an undefined 'preset' concept requires far more than one sentence. An agent cannot determine what a preset does, what the apply/dry_run flags trigger, or what a successful call changes.

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 29% (7 params, 2 described), so the description must compensate and does not. It says nothing about `apply`, `dry_run`, `preset` values, or campaign targeting, and adds no meaning beyond the two schema-documented account fields.

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 verb ('apply') and a resource ('strategy preset to a campaign'), so the agent knows this mutates campaign strategy. However, 'preset' is never defined (what presets exist, what settings they set), and the description does not distinguish it from the many sibling set_campaign_* tools that also configure campaigns.

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 when to prefer this over direct.hf.set_campaign_budget, set_campaign_geo, or the other set_campaign_* siblings. The only hint is the 'Human-friendly' prefix, which is a naming convention rather than usage guidance.

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