google_ads_location_targeting_list

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

No annotations are provided, so the description bears the full burden. It states the tool is read-only, returns a list of objects with specific fields and an example, and explains geo_target_constant mapping. It does not cover error handling or pagination, but overall it provides good transparency for a list tool.

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, front-loaded with the action and return type, and uses three sentences that each add value without redundancy. It efficiently communicates purpose, return structure, and usage context.

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 no output schema, the description adequately describes the return format with an example. It covers read-only nature, sibling differentiation, and provides guidance on geo_target_constant lookup. The tool's purpose is fully covered for an agent to invoke it correctly.

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 100%, so baseline is 3. The description does not add additional meaning to the parameters beyond what the schema already provides (e.g., the schema already describes customer_id fallback and campaign_id source). No extra parameter details in the description.

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 tool lists every location campaign criterion on a Google Ads campaign, specifies the return format with fields like criterion_id and geo_target_constant, and differentiates from siblings like google_ads_location_targeting_update and google_ads_schedule_targeting_list.

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 explicitly tells when to use this tool vs alternatives: 'For adding or removing locations use google_ads_location_targeting_update; for schedule-based targeting use google_ads_schedule_targeting_list.' It also advises on looking up geo target constants via GeoTargetConstantService.

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