google_ads_conversions_performance

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

Discloses read-only nature, explains the reason for separate GAQL query for cost_per_conversion, and details the output structure including sorting. With no annotations provided, 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?

The description is relatively concise for the amount of information provided. It fronts the purpose and data structure. Could be slightly shorter, but all sentences add value.

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 no output schema, the description fully details the return structure (period, campaign_id, total_conversions, actions, daily_details, landing_pages) with sorting and filtering rules. It also explains the cost_per_conversion computation. Complete for a reporting 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?

All three parameters have schema descriptions (100% coverage). The description adds usage context for period parameter (e.g., 'Use LAST_7_DAYS / LAST_14_DAYS for recent diagnosis; LAST_90_DAYS for baseline.') and explains customer_id fallback logic.

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 reports Google Ads conversions broken down by conversion_action and date with optional campaign filter. It distinguishes from sibling tool google_ads_performance_report for campaign-level metrics.

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 mentions when to use (for conversion performance by action/date) and when not (use google_ads_performance_report for campaign-level metrics). It also explains that only rows with conversions > 0 are included and the cost_per_conversion computation limitation.

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