list_ad_groups

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

No annotations are provided, so the description carries the full burden. It correctly implies a read-only list operation and hints at the return shape by mentioning ad_group_id, but does not disclose pagination behavior, default account context, or response format beyond IDs. This is a moderate gap for a list operation.

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?

Two concise sentences with the primary action and key optional filter front-loaded, plus downstream usage guidance. No unnecessary words or repetition.

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 8 parameters, no annotations, and no output schema, the description is too sparse. It omits how pagination works, whether ad_account_id is ever required, what the default limit is, and the nature of the returned objects. An agent might correctly call the tool without knowing the full behavior or constraints.

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%, with four params undocumented (after, limit, order, before). The description only mentions campaign_id, which is already described in the schema, and does not add meaning for pagination, ordering, or includes. It fails to compensate for the undocumented parameters.

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 verb 'List', the resource 'ad groups for the ad account', and an optional filter by campaign_id. It also explains how to use the output (ad_group_id) for downstream actions, distinguishing it from list_campaigns, list_ads, and get_ad_group.

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?

Provides clear context: this is for listing ad groups and filtering by campaign_id, with a note on using the returned IDs for creating ads or fetching insights. It does not explicitly name alternatives or exclusion criteria, but the context is sufficient for typical selection among sibling tools.

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