ad_groups_query

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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint, so the safety profile is covered. The description adds only 'bounded' and 'endpoint-specific filters', which are vague and largely restate schema concepts; it does not explain pagination behavior, result breadth, or the meaning of endpoint-specific beyond what structured fields already provide.

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, front-loaded sentence with no filler. It is appropriately sized, though its brevity contributes to under-specification rather than being a model of economical clarity.

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 12-parameter query tool with many overlapping siblings, the description is too thin. Even with an output schema and rich annotations, it does not clarify the tool's scope, endpoint-specific behavior, or how it relates to ad_group_get and ad_group_report.

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 all 12 parameters are already documented in the input schema. The description mentions 'filters' but adds no syntax, constraints, or prioritization beyond the schema, which is the expected baseline when 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 states a verb and resource ('Query ... ad groups') and adds a qualifier ('bounded', 'endpoint-specific filters'), so the broad function is clear. However, it does not distinguish this tool from closely named siblings such as ad_group_get, ad_group_report, ads_query, or keyword_report, leaving the specific purpose ambiguous.

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 gives no conditions for when to use this tool versus alternatives. It does not mention prerequisites, when to avoid it, or how it differs from ad_group_get or ad_group_report, so an agent must infer usage from the name and schema alone.

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