List Google Ads Campaigns

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

Annotations already provide readOnlyHint, idempotentHint, and destructiveHint. The description adds useful output field details but does not disclose additional behavioral traits (e.g., pagination behavior, authentication requirements, or potential performance implications).

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 a single sentence that effectively conveys the tool's purpose and output. It is appropriately sized, front-loaded, and contains no extraneous information.

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?

While the description covers basic intent and output fields, it is missing context on pagination (despite page_size parameter), default behavior, and any assumptions about the customer_id. The output schema exists, so return values are documented, but the description could be more complete for a list operation with multiple parameters.

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 only 60%, with parameters page_size and response_format lacking descriptions. The description does not add meaning to these parameters; it only describes output fields. It fails to compensate for the gaps in schema documentation.

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?

Description clearly states the verb 'List', the resource 'campaigns under a Google Ads customer', and enumerates specific output fields. This distinguishes it from siblings like google_ads_get_campaign (single campaign) and google_ads_list_ad_groups (different resource).

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 does not explicitly state when to use this tool versus alternatives like google_ads_get_campaign or google_ads_list_ad_groups. While it implies listing all campaigns, it lacks direct usage guidance or exclusion criteria.

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