List ad groups

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

Annotations provide readOnlyHint and openWorldHint, which cover basic behavioral traits. The description adds no extra behavioral details beyond the parameter requirement. It does not contradict annotations, so a score of 3 is appropriate.

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 no unnecessary words. Every sentence adds information: the first states the purpose, the second provides critical usage instructions. No fluff.

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 no output schema and well-documented parameters, the description covers the essential points. It specifies what the tool does and the key requirement. Minor improvements could include noting that it returns a list of ad groups, but the purpose is clear.

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 coverage is 100%, so baseline is 3. The description adds value by highlighting that campaignIds and/or ids are required as selection criteria, which goes beyond the schema's individual field descriptions. This aids the agent in understanding parameter relationships.

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 'Lists ad groups' with a specific verb and resource. It distinguishes from sibling list tools like list_ads and list_campaigns by naming the resource. The additional context about requiring at least one selection criterion further clarifies the tool's role.

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 explicitly instructs users to provide campaignIds and/or ids and notes the API requirement for at least one selection criterion. This serves as a clear usage guideline. While it doesn't explicitly mention when not to use this tool or name alternatives, the sibling list provides context.

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