google_ads_location_targeting_list

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

The description declares 'Read-only' and details the output format (criterion_id, geo_target_constant, bid_modifier), explaining the meaning of geo target constant IDs and how to look them up. While no annotations exist, it covers the key behavioral traits for a read operation. Could be improved by mentioning required permissions or additional side effects, but sufficient.

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?

Concise and efficient: first sentence states main purpose, then output format, read-only note, lookup guidance, and sibling references. Every sentence adds value 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?

Given the tool's complexity (listing location criteria on a campaign) and the lack of output schema, the description fully explains the output structure and provides necessary context (e.g., geo target constant lookup). No 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?

Schema coverage is 100%, so baseline is 3. The description adds meaning by explaining that customer_id is optional with fallback to credentials, and campaign_id is required and obtainable via google_ads_campaigns_list. This enriches understanding beyond the schema definitions.

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?

Clear verb ('List') and resource ('LOCATION campaign_criterion on a Google Ads campaign') with specific scope. Distinguishes from siblings like google_ads_location_targeting_update and google_ads_schedule_targeting_list by explicitly naming them.

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?

Explicitly states when to use this tool (listing locations) and when to use alternatives: 'For adding or removing locations use google_ads_location_targeting_update; for schedule-based targeting use google_ads_schedule_targeting_list.' Provides clear context for selection.

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