google_ads_recommendations_list

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

No annotations provided, so description carries full burden. It declares read-only and explains the return structure with example fields. Additional context like filtering behavior is included, though no mention of rate limits or auth requirements.

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?

Description is concise and front-loaded with action. Every sentence adds value: action, return format, read-only note, filtering options, and cross-reference to apply tool. No wasted words.

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?

Despite no output schema, description clearly details the return structure (array of objects with fields). It covers parameter usage, read-only nature, and relationship to sibling. Complete for a list tool.

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 coverage is 100% with all parameters described in input schema. The description adds value by explaining how to filter: 'Filter by campaign_id to scope to one campaign, or by recommendation_type to scope to one kind.'

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 clearly states the tool lists Google Ads recommendations and details the return format (resource_name, type, impact). It is specific and distinguishes from sibling tool 'google_ads_recommendations_apply'.

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?

Explicitly notes read-only nature and filtering by campaign_id or recommendation_type. References the apply tool for actions. Although no explicit 'when not to use', it provides clear context and alternatives.

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