direct.hf.set_bid_modifier_desktop

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, and it says almost nothing. For a mutation tool with apply and dry_run flags, it does not explain whether changes are live immediately, what dry_run does, or what permissions/scope are required. 'Human-friendly' is an unexplained label rather than disclosed behavior.

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?

A single short, front-loaded sentence with no padding — nothing is wasted, but it is thin rather than efficient. It is adequately sized for the purpose it attempts but is under-specified given seven parameters and a write operation.

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?

Seven parameters with zero required and no annotations, no output schema, and no return-value explanation. The description never covers the apply/dry_run workflow or how a campaign is targeted, so an agent cannot confidently construct a call from this definition alone.

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% (account_id and direct_client_login are documented). The description's 'percent' does clarify the unit for value_percent, which is genuinely useful since an agent could otherwise pass 1.5 or 150. But apply, dry_run, campaign_id, and campaign_name remain undocumented in both the schema and the description.

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 (set), resource (bid modifier), a platform scope (desktop) and the unit (percent), which cleanly distinguishes it from the sibling set_bid_modifier_mobile. It does not, however, name those siblings explicitly or clarify how it relates to set_bid_modifier_demographics/geo, so an agent must infer the distinction. Clear but not sibling-differentiating.

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. The word 'desktop' implicitly routes away from the mobile/demographics/geo variants, but the agent is left to work out that these are mutually exclusive targeting dimensions on its own. No exclusions or conditions are stated.

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