list_ad_groups

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

With no annotations provided, the description carries the burden of behavioral disclosure. It reveals the return fields and the optional filter, which is useful, but it does not mention potential pagination, default sort order, or whether inactive ad groups are included, leaving gaps in transparency.

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, front-loaded sentence that immediately states the primary verb and resource, followed by essential scope and return-value details. Every word adds value, and there is no redundancy or filler.

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 with two parameters and no output schema, the description provides the essential context: what it lists, the optional filter, and the returned fields. It could add pagination or filtering details, but the current description is largely complete for typical agent 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 0%, so the description must compensate. It clarifies that campaign_id is an optional filter ('optionally filtered to one campaign'), but it does not explain customer_id beyond what the schema's title implies. This partial clarification aligns with a mid-range score.

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's action ('List ad groups') with a specific resource and optional scope ('optionally filtered to one campaign'). It also lists the returned fields, which distinguishes it from sibling tools like list_ads and list_keywords.

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 implies usage when ad groups are needed and explains the optional campaign filter, but it does not explicitly state when to use this tool over alternatives like list_campaigns or list_ads, nor does it provide exclusions or prerequisites.

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