get_ad_groups_tool

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

No annotations are present, so the description carries the full burden. It does not disclose pagination behavior (implied by page/page_size), the nature of filters, or any side effects (e.g., read-only). The bare statement 'Get ad groups' suggests a safe read operation but lacks critical behavioral context.

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, making it concise. However, it lacks structure (e.g., separate lines for purpose, usage, parameters) and is arguably too terse for a tool with 5 parameters and an output schema.

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?

Given the tool has 5 parameters, nested objects, and an output schema, the description is severely incomplete. It does not explain pagination, filter syntax, campaign constraints, or the structure of the response. The output schema exists but the description should still provide an overview of the return value.

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%, meaning the input schema provides no parameter descriptions. The description only mentions 'optional filtering' without explaining the `filters` object, `page`, `page_size`, or `campaign_id` parameters. This adds almost no value over the schema itself.

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 'Get' and resource 'ad groups', and specifies the scope 'for a specific advertiser' with optional filtering. This distinguishes it from sibling tools like get_ads_tool or get_campaigns_tool, which target different resources.

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?

No guidance is provided on when to use this tool versus alternatives or what prerequisites are needed. The description only implies use when retrieving ad groups for an advertiser, but fails to mention exclusions or comparisons to siblings.

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