google_ads_conversions_performance

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

Discloses that only rows with conversions > 0 are included, cost_per_conversion is computed separately due to GAQL limitations, and that it is read-only. No annotations provided, so description carries full burden and does well.

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 moderately long but well-structured, front-loaded with purpose and output shape. Every sentence adds value, though could be slightly more 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?

No output schema, but description provides detailed output structure, explains edge cases (conversions > 0), and covers all relevant aspects. 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?

Schema coverage is 100%, but description adds context: period usage recommendations, customer_id fallback behavior, and campaign_id optionality. Adds value beyond 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?

Description clearly states it reports Google Ads conversions broken down by conversion_action and date with optional campaign filter. Provides detailed output structure and distinguishes from sibling tool google_ads_performance_report.

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 directs to use google_ads_performance_report for campaign-level metrics. Provides guidance on period selection (e.g., LAST_7_DAYS for recent diagnosis). Does not explicitly state when not to use, but alternative is named.

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