google ads get campaigns

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

Annotations already cover the safety profile (readOnlyHint, idempotentHint, destructiveHint, openWorldHint), so the description does not need to repeat it. It adds a little context by specifying the returned campaign fields, but it does not disclose pagination or partial-result behavior beyond what the schema mentions.

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 with no filler, front-loading the action and the resource. It is appropriately sized for a simple list tool with a rich schema and annotations.

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?

With all parameters fully documented in the schema)Skip and an output schema present, the description supplies enough for an agent to invoke the tool correctly. It could be more complete by noting when to prefer sibling tools like google_ads_run_gaql, but that is not essential for basic use.

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 100%, so all parameters are already fully documented. The description's 'for a Google Ads account' loosely maps to customerId but adds no parameter meaning beyond the schema. Baseline 3 is appropriate here.

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 names a concrete resource (campaigns), uses the specific verb 'List', and notes the fields it returns (status, budget, channel type, bidding strategy). It does not explicitly differentiate from sibling list tools like google_ads_get_adgroups or google_ads_get_budgets, so it stops short of a 5.

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 phrase 'List campaigns for a Google Ads account' implies when to use the tool: when campaign-level entities are needed. However, there is no explicit when-not-to-use guidance or mention of alternatives such as google_ads_run_gaql for more flexible queries, leaving the routing partly implied.

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