direct.hf.set_campaign_negative_keywords

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 for a mutation tool. Critically, 'set' is ambiguous about whether the existing negative keyword list is replaced or appended to, and nothing explains the apply vs dry_run behavior or required auth (e.g., direct_client_login).

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 sentence is short and front-loaded, but the 'Human-friendly:' prefix is filler that earns no place, and the extreme brevity is under-specification rather than efficient conciseness.

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 a 7-parameter mutation tool with no annotations and no output schema, this one-line description is wholly inadequate. An agent lacks the information needed to safely set negative keywords, especially the replace-vs-append semantics and the apply/dry_run contract.

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?

Seven parameters exist with only 29% schema description coverage, and the description mentions none of them. It gives no meaning for items, apply, dry_run, campaign_id vs campaign_name, or the two documented override params, so it fails 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+resource combination (set negative keywords for a campaign), so an agent knows the operation. However, it does not distinguish this from the close sibling direct.hf.set_adgroup_negative_keywords, which sets the same kind of entity at a different scope.

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 guidance on when to use this versus the adgroup-level variant, nor any mention of prerequisites or the apply/dry_run workflow. The agent is left to infer everything from the name alone.

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