direct.hf.set_autotargeting_bid

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 discloses only the currency (rubles); it says nothing about whether this mutates state, what apply/dry_run do, or whether authentication via Direct Client-Login is required, all of which matter for an unattended agent.

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 sentence with the action front-loaded, so there is no padding. The brevity is under-specification rather than elegance, and the '---autotargeting' notation is confusing without explanation.

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 mutation tool with no annotations, no output schema, and only partial schema coverage, the description should explain the apply/dry_run safety pattern, the bid semantics, and how campaigns are identified. Instead it provides only a one-line label, leaving the agent without enough to call it safely.

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), and the description does not compensate: apply, bid_rub, dry_run, campaign_id, and campaign_name are undocumented in both places. The '(rubles)' hint loosely relates to bid_rub but never names or explains the parameter, its interaction with dry_run/apply, or how campaign targeting is resolved.

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 verb (set bid) and a resource (autotargeting pseudo-keywords) plus a currency unit, which is more specific than a tautology. However, the '---autotargeting pseudo-keywords' phrasing is cryptic and it offers no differentiation from the many sibling bid tools such as direct.hf.set_keyword_bid or direct.hf.set_keyword_bids_bulk.

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 tool versus set_keyword_bid, set_keyword_bids_bulk, or the bid-modifier siblings, nor any mention of prerequisites. The word 'Human-friendly' hints at a convenience wrapper but does not translate into an actionable selection criterion.

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