google_ads_campaigns_list

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

No annotations are provided, so the description must disclose behavior. It explicitly states 'Read-only' and describes the row-per-campaign return format including the specific fields returned. While it doesn't mention pagination or rate limits, the read-only nature and return shape are well covered.

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?

Three sentences: first states the action, second describes output and read-only nature, third provides usage and alternative tool. Every sentence adds value, and the structure is front-loaded with the core purpose.

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?

For a simple list tool, the description is complete: it covers what it returns, when to use it, the read-only aspect, and the alternative for single-campaign details. The schema provides parameter details, and no output schema is needed since the return fields are enumerated in the description.

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 input schema fully documents both parameters with descriptions and enums (100% coverage). The description adds no extra parameter information beyond referencing 'optional status filtering', so a baseline score of 3 is appropriate since the schema does the heavy lifting.

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, distinguishing it from the sibling google_ads_campaigns_get which returns full details for a single campaign. It also specifies the exact output shape (id, name, status, etc.), making the purpose unambiguous.

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 says to use this tool to audit account structure or find a campaign_id before calling campaigns.get/update/update_status, and directs users to google_ads_campaigns_get for single-campaign details. This provides clear when-to-use and alternative guidance.

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