List ad groups

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered structurally. The only added context is the REST endpoint 'GET /v1/ad-groups', which tells the agent nothing about pagination, result size, default ordering, or whether filters are ANDed. For a list tool whose output shape is undocumented, that is thin.

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?

A single sentence with no wasted words and the endpoint front-loaded, so structure is fine. However the brevity is under-specification rather than discipline; there is no second sentence carrying the filtering or return-value context an agent needs.

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?

Two optional filters with no output schema and no parameter descriptions mean the description should explain what is returned and how the filters combine, and it does neither. Against a many-sibling tool family, this leaves the agent guessing at default behavior.

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 mentions neither 'status' nor 'campaignId'. The enum values under EntityStatus are the only hint, and the description does not compensate for the coverage gap, so meaning beyond the raw schema is essentially absent.

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?

Names a specific verb and resource: 'List ad groups'. That is enough to separate it from adGroups_create, adGroups_update and ads_list without opening schemas. It stops short of stating scope (all ad groups vs. filtered), so it is clear but not distinctive.

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 on when to call this versus adGroups_create/adGroups_update or ads_list, and no mention of whether the filters are optional narrowing or required context. The agent must infer that this is the read/discovery entry point from the name alone.

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