list_campaign_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 of behavioral disclosure. 'List' implies a read-only operation, but the description does not mention authentication requirements, pagination, response shape, or any side effects. It adds little beyond what the tool name already conveys.

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 short sentence with no wasted words. However, it largely restates the tool name and adds minimal value, so it is concise without being substantive. Front-loading is not an issue given its brevity.

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?

The tool has an output schema and two optional parameters with defaults, so basic invocation is inferable. But with no annotations, no usage guidance, and no parameter semantics in the description, the definition is not complete enough for an agent to reliably select and invoke this tool in the right context.

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%, and the description provides no explanation of the path or query_json parameters. The schema shows defaults like '/rest/adCampaignGroups' and '{}', but the description does not clarify how query_json should be structured or what values path accepts. With 0% coverage, the description must compensate and fails to do so.

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 states a specific verb and resource: 'List ad campaign groups.' This is clear and identifies the resource as ad campaign groups, which helps distinguish it from the sibling list_campaigns at a basic level. However, it does not explicitly differentiate campaign groups from campaigns or other list operations.

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 about when to use this tool versus alternatives like list_campaigns, create_campaign_group, or the auth-related tools. The description merely states what it does, leaving the agent to infer appropriate usage from the name and context.

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