ad_manager_li_get_campaign_group_reporting

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

The annotations already indicate readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. However, the description adds no behavioral context beyond the verb, such as data aggregation, auth requirements, or response format. It does not contradict annotations, but it fails to disclose any additional behavioral traits.

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 concise phrase with no fluff, front-loading the verb and resource. While it is appropriately short, it is somewhat under-specified, but structurally it is efficient and clear.

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?

There is no output schema, so the description should explain what reporting data is returned (e.g., metrics, dimensions) and how the fields parameter affects output. It also lacks any note on pagination or format. The description leaves the agent uncertain about the response structure.

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 100%, so the schema fully documents each parameter. The tool description itself adds no parameter-specific information. Baseline is 3 since the schema does the heavy lifting.

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 'Get campaign group reporting' clearly states a verb and resource, indicating it retrieves reporting data for a campaign group. It distinguishes from sibling tools like ad_manager_li_get_ad_analytics by specifying the entity (campaign group vs. ads), though it does not specify what kind of reporting metrics are included.

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?

There is no guidance on when to use this tool versus alternatives like ad_manager_li_get_reporting_list or similar reporting tools for other platforms. The description does not mention any exclusions, prerequisites, or scenarios where this tool is preferred.

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