direct.hf.set_bid_modifier_demographics

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. 'Human-friendly' and 'set' imply a mutation wrapper, but it omits auth requirements, dry_run/apply semantics, reversibility, and what happens to existing modifiers.

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 waste-free, but it is too sparse for a 9-parameter mutation tool. The 'Human-friendly:' prefix adds little value while the rest under-specifies rather than conveys necessary structure.

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 9-parameter mutation tool with no annotations, no output schema, 22% schema coverage, and operational parameters like apply, dry_run, and value_percent, one sentence is grossly incomplete. An agent cannot call it correctly without guessing.

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 22% (2 of 9 parameters documented). The description mentions age and gender but gives no meaning for value_percent, apply, dry_run, campaign_id, campaign_name, or how account_id resolves defaults, so it does not compensate for low schema coverage.

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 specific verb ('set'), resource ('bid modifier'), and demographic scope ('age+gender'), which distinguishes it from sibling bid-modifier tools for mobile, desktop, and geo. However, it does not state whether the modifier applies at campaign or adgroup level, keeping it from a 5.

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, when-not, or alternatives are provided. It does not explain its relationship to siblings like direct.hf.set_bid_modifier_mobile, direct.hf.set_bid_modifier_desktop, or direct.hf.clear_bid_modifiers.

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