list_adgroups

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 explains that with_details=True (default) adds bid/budget/period details, implying a read operation. However, it does not explicitly state that the tool is idempotent or non-destructive, though the context strongly suggests it.

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 well-structured with a summary line, usage examples, a warning, and parameter explanations. It is slightly long but every sentence adds value; no 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?

Given two parameters, no output schema, and no annotations, the description covers purpose, parameters, and usage guidance adequately. It could be more explicit about the return format (e.g., array of objects), but the with_details parameter implies the structure. Overall fairly complete for a list tool.

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%, but the description explains both parameters: campaign_id is 'close to required' for filtering by campaign, and with_details (default true) reinforces details per ad group. This adds significant meaning beyond the schema types and defaults.

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 it lists ad groups within a specific campaign with details like bid, daily budget, execution period, and device. It provides example questions that illustrate its purpose, and distinguishes from sibling list_campaigns by focusing on ad groups.

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?

Explicit usage guidance is given with example questions (e.g., 'show ad groups of campaign X') and a clear warning: if only ad group ID is known, first use list_campaigns to find the campaign. This directly helps the agent decide when to use this tool.

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