google_ads_set_device_bid_adjustments

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

No annotations are provided, so the description carries full burden. It explains the effect (increase/decrease bids), the range (0.1 to 10.0), and default behavior (1.0 = no change). However, it does not disclose whether it overwrites existing adjustments, required permissions, or error handling for out-of-range values.

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 description is concise and well-structured: a brief intro, common adjustments list, parameter definitions, return statement, and a clear example. Every sentence adds value, and the layout aids readability.

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?

The description covers the tool's purpose, parameters, range, default behavior, and includes an example. It explains what the tool does and returns. It lacks only minor details like error cases or validation, but for a setter tool with a straightforward output, it is quite complete.

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 0%, but the description lists each parameter with its purpose and valid range (e.g., mobile_modifier: 0.1 to 10.0). The 'Args' section and example add significant meaning beyond the schema, which only provides types and titles.

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 clearly states 'Set bid adjustments for different device types', using a specific verb and resource. It distinguishes from siblings like 'google_ads_list_bid_adjustments' (list) and 'google_ads_set_ad_schedule_bid_adjustments' (schedule), as well as other set tools.

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?

The description explains the purpose and range of bid modifiers, with common examples, but does not explicitly direct when to use this tool over alternatives (e.g., when to set device vs ad schedule adjustments). It implies usage but lacks explicit exclusions or comparisons.

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