set_location_bid_modifiers

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

With no annotations provided, the description carries the full transparency burden and does so thoroughly. It discloses the allowed percent range, zero-removes semantics, bidding-strategy limitations, rejection of untargeted geos, atomic mutation, and the dry-run-before-confirm 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?

The description is dense but fully front-loaded: core action and constraints come first, followed by parameter format, behavioral caveats, and confirmation semantics. Every sentence adds necessary operational detail without redundancy.

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 complex mutation tool with no annotations, the description covers all critical decision factors: range, target constraints, bidding-strategy compatibility, atomicity, and dry-run behavior. An output schema exists, so return-value details are not required here.

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 description coverage is 0%, so the description must explain parameters, and it does. It details the modifiers map format with concrete examples, accepts both raw IDs and geoTargetConstants/ prefixed IDs, explains that 0 removes an adjustment, and clarifies confirm's dry-run default.

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 opens with a specific verb and resource: 'Set campaign-level LOCATION bid adjustments'. It clearly distinguishes this from sibling tools like set_device_bid_modifiers by explicitly naming the campaign-level location scope.

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?

It specifies when the tool is effective by stating location adjustments are honored by Manual CPC and Maximize clicks but ignored by Smart Bidding, giving clear guidance on when not to use it. It also clarifies that targeting is never changed and only already-targeted locations are accepted.

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