google_ads_campaigns_list

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

No annotations are provided, so description carries full burden. It states 'Read-only' explicitly and describes output fields. However, it does not disclose potential pagination behavior, rate limits, or handling of large accounts. For a list endpoint, some behavioral context is missing.

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, no unnecessary words. First sentence states purpose, second lists return fields, third provides usage guidance and alternative. Highly efficient.

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 endpoint with no output schema, the description covers purpose, parameter behavior, output fields, and use cases. It lacks only minor details like pagination, but overall complete for the tool's complexity.

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 value by clarifying that customer_id is optional and falls back to env vars, and that omitting status_filter returns all statuses including REMOVED. This goes beyond the schema.

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 'Lists campaigns in a Google Ads account' and specifies the returned fields (id, name, status, etc.). It distinguishes from siblings like campaigns_get by noting 'use this to... find a campaign_id before calling campaigns.get / update / update_status' and 'For a single campaign's full details use google_ads_campaigns_get instead.'

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 mentions when to use this tool: 'Use this to audit account structure or find a campaign_id before calling campaigns.get / update / update_status.' Also advises an alternative: 'For a single campaign's full details use google_ads_campaigns_get instead.' No ambiguity.

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