google_ads_get_adgroups

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

With no annotations, the description must carry disclosure weight. 'List' signals a read-only operation and the optional campaign filter is stated, but it does not mention pagination behavior, how missing statusFilter is treated, or what response shape to expect.

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?

A single, front-loaded sentence conveys the resource, scope, and main optional behavior with no filler or redundancy.

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?

This is a simple list operation and the description covers its core purpose, but without an output schema or any mention of filtering defaults/response behavior, the agent is left to infer some operational details. It is adequate but not comprehensive.

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 50%, covering customerId and campaignId. The description loosely reinforces the campaign filter but adds no detail about limit or statusFilter. The enum values and default on limit are self-explanatory enough to keep this adequate but not strong.

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 uses a specific verb ('List'), names the resource ('ad groups'), and scopes it to a Google Ads account with an optional campaign filter. This clearly differentiates it from sibling tools like google_ads_get_campaigns and account-level tools.

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 intended use is implied: call this when you need ad groups for an account, optionally narrowed by campaign. However, it gives no explicit guidance about when to prefer this over alternatives like google_ads_run_gaql or how it relates to the large set of sibling getter tools.

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