google_ads_get_recommendations

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

No annotations exist, so the description carries the behavioral burden. 'List' implies a read-only operation and 'when supported' adds a caveat about impact, which is useful. It does not state pagination/limit semantics or required customer context, though for a list operation these are minor.

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, front-loaded sentence with no filler; the key verb/resource and output attributes are packed efficiently, and the 'when supported' caveat is concise.

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 simple read-only list tool, this is largely complete: schema supplies required customerId, limit bounds, and typeFilter format; description supplies return-field context. Without an output schema or annotations, a little more about response format or pagination would be nice, but the definition is usable.

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 only 50%, and the description does not compensate for the undocumented `limit` and `includeDismissed` parameters. It only describes output fields; it adds no meaning to the input parameters beyond what the schema already provides.

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 uses a specific verb ('List') and a specific resource ('Google Ads recommendations'), then enumerates the returned dimensions (type, resource, links, dismissed state, impact). This clearly distinguishes it from sibling tools because no other sibling targets recommendations.

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 tool name and description imply the use case: any time recommendation data is needed. However, it names no alternatives and gives no exclusions, leaving the agent to infer rather than receive explicit routing guidance.

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