google_ads_auction_insights_analyze

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

Discloses read-only nature, API limitations (v23 removed competitor-level data), insight triggering thresholds, return structure including field names and types. With no annotations, the description fully covers behavioral traits.

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?

Every sentence adds value. Front-loaded with purpose, then details, then alternative usage. No unnecessary 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, the description fully explains the return structure and insight generation logic. Given the complexity (3 params, API limitations), the description is complete.

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%, and description adds extra context: default period, recommendation for choosing period based on use case, fallback behavior for customer_id, and how to obtain campaign_id from another tool.

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 interprets impression-share metrics and surfaces human-readable insights about competitive position. It distinguishes itself from sibling tool google_ads_auction_insights_get which provides raw metrics without insights.

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 says when to use this tool vs. alternatives: 'For the raw metrics without insights use google_ads_auction_insights_get; full competitor data is only available in the Google Ads UI.' Also provides guidance on using shorter/longer periods for different diagnostic needs.

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