direct.hf.set_bid_modifier_geo

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

No annotations exist, so the description carries the full behavioral burden. 'Best effort' hints that application may be partial or non-atomic, which is genuinely useful, but there is nothing about whether this requires apply=true, what dry_run does, permissions, or what state is mutated.

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 it is under-specified rather than truly concise, and the 'Human-friendly:' label is pure filler for a 7-parameter mutation tool.

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 write tool with zero annotations, 29% schema coverage, no required-parameter indication, and no output schema, this description is far too thin; an agent has almost no basis for calling it safely or correctly.

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% across 7 parameters, so the description should compensate, yet it explains none of them. 'geo' loosely implies region_id and 'bid modifier' implies value_percent, but apply, dry_run, campaign_id, and the client-login override are left entirely to bare types.

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 names a specific verb+resource ('set geo bid modifier') and the word 'geo' implicitly separates it from the sibling tools set_bid_modifier_mobile/desktop/demographics. The 'Human-friendly' prefix is filler that adds nothing to identifying the action.

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 when-to-use guidance, no prerequisites, and no named alternative. An agent must infer from the term 'geo' alone that this covers regional bid adjustments rather than device or demographic ones, which is never stated.

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