google_ads_campaigns_list

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

The description explicitly states 'Read-only,' which is a key behavioral trait given no annotations are provided. It also mentions the fallback behavior for customer_id and the output format. However, it does not discuss pagination, rate limits, or error handling, but for a list tool with clear read-only nature, the transparency is adequate.

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 paragraph of four sentences, each providing essential information without redundancy. It is well-structured, starting with the main action, then output details, usage guidance, and a clear alternative.

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 absence of output schema, the description adequately covers the return fields, purpose, usage guidelines, and parameter behavior. It provides all necessary context for an agent to use the tool correctly and understand its outputs.

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 value beyond the input schema: it explains that customer_id is optional and falls back to environment variables, and it describes the return fields alongside the parameters. Schema coverage is 100%, but the description enriches understanding of parameter behavior and context.

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 campaigns in a Google Ads account with optional status filtering, and specifies the returned fields (id, name, status, etc.). It distinguishes itself from the sibling tools by mentioning that for a single campaign's full details, google_ads_campaigns_get should be used.

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 states when to use this tool: to audit account structure or find campaign_id before calling campaigns.get/update/update_status. It also provides the alternative: for a single campaign's full details, use google_ads_campaigns_get.

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