google_ads_recommendations_apply

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

No annotations are provided, so the description carries the full burden. It clearly states the mutation is committed immediately and not reversible. It mentions server-side re-validation and lists example changes (new keyword, ad copy, bidding strategy switch). It could mention permissions or rate limits but still provides solid behavioral context.

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 paragraph but packs important information without unnecessary fluff. It could be slightly more structured (e.g., separate sections), but it is concise and front-loads the key action and side effects.

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?

Given the tool's simplicity (2 parameters, no output schema), the description covers the necessary context: what it does, return value, non-reversibility, and relationship to list tool. It does not miss critical information for this tool type.

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%, so baseline is 3. The description adds value by explaining that customer_id is optional with fallback to credentials, and that resource_name must be exactly as returned by the list tool and is re-validated. It also specifies the format pattern. This goes beyond the schema.

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 'Apply one Google Ads recommendation by resource name.' It uses a specific verb (apply) and resource (recommendation). It distinguishes itself from sibling tools like google_ads_recommendations_list, which is used to list candidates.

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 explicitly provides usage guidance by stating 'To list candidates use google_ads_recommendations_list' and notes that some recommendation types change budget, device, or schedule. This helps the agent decide when to use this tool versus others.

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