google_ads_set_campaign_locations

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

No annotations are provided, so the description must fully disclose behavior. It indicates a write operation ('Set') but does not explain whether it overwrites or appends locations, if changes are reversible, or what the exact response contains beyond 'Success message'. This leaves ambiguity for the 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?

The description is well-structured with clear sections (Args, Returns, Note), concise sentences, and no redundant information. It is front-loaded with the purpose and efficiently conveys all necessary details.

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?

Given the tool's moderate complexity, the description covers core functionality and parameter details but lacks behavioral context (e.g., idempotency, permission requirements) and detailed return value specification. The output schema is mentioned but not explained, leaving some gaps.

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?

The description adds significant value over the input schema by explaining each parameter's purpose, including formatting hints ('without hyphens'), the optional nature of 'negative_location_ids', and providing a helpful note with common location IDs. Schema coverage is 0% in context signals, so the description fully compensates.

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 the action 'Set location targeting for a campaign' with specific verb and resource. It distinguishes from sibling tools like 'google_ads_set_campaign_languages' and 'google_ads_set_campaign_schedule' by focusing on locations.

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 implies usage when setting campaign locations but does not explicitly state when to use this tool versus alternatives like 'google_ads_get_campaign_details' or other setup tools. No exclusions or alternative recommendations are provided.

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