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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is fully carried by structured data. The description adds one genuinely useful behavioral fact — removed campaigns are excluded — but says nothing about pagination, result limits, or external-API latency, which matter for an openWorld connector.

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?

One short, front-loaded clause with zero padding or repetition. It loses a point only because the fragmentary punctuation makes it read as a truncated label rather than a deliberate sentence.

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?

This is a low-complexity read with one optional parameter, full schema coverage, and complete annotations, so not much is required. The description does list the returned fields (status, type, daily budget), which partially compensates for the missing output schema, but pagination and result-size behavior remain undocumented.

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%, and the single optional project_id is fully documented in the schema including its 'leave out for the default' behavior. The description adds no parameter meaning beyond that, so the baseline 3 applies.

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 phrase 'The Google Ads campaigns (not removed): status, type and daily budget' names the resource and the fields returned, so the intent (retrieve a list) is inferable, but the verb is never stated and the fragment style reads as a label rather than a statement of what the tool does. It also does not distinguish this from the sibling google_ads_campaign_stats, which an agent could easily confuse with it.

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 explicit when-to-use guidance: nothing says when to pick this over google_ads_campaign_stats or how it relates to project scoping. The only implied constraint, 'not removed', hints at a default filter but is not framed as usage guidance or an exclusion.

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