google_ads_conversions_performance

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

Despite no annotations, the description comprehensively covers behavioral aspects: return structure (actions, daily_details, landing_pages), sorting, filtering (only rows with conversions > 0), computation limitation (cost_per_conversion via separate GAQL), and declares read-only nature.

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 informative but slightly verbose due to detailed return structure. It is well-structured: summary, then return format details, then behavioral notes, and sibling differentiation. Every sentence adds value, but 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?

Given no output schema, the description provides a thorough return structure and covers all important aspects: parameters, usage, behavioral constraints, and output format. It is fully self-contained and leaves no critical gaps.

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 the optional nature of campaign_id, default period, and providing usage recommendations for different periods (recent diagnosis vs. baseline).

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 itself from sibling google_ads_performance_report by specifying it provides conversion action breakdown, not just 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 states when to use this tool (conversion breakdown) and when not to: 'For campaign-level metrics use google_ads_performance_report.' Provides clear alternative for different needs.

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