google_ads_conversion_summary_report

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

No annotations provided, so description should disclose behavioral traits. It does not mention read-only nature, potential rate limits, required permissions, or any side effects. The description merely states the function without 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?

Description is concise, well-structured with Args, Returns, and Example sections. It uses minimal words effectively, though the example could be integrated more naturally. No redundant content.

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 low complexity and presence of output schema, description covers basic purpose and parameter usage. However, it lacks usage guidelines and behavioral transparency, which are necessary for complete contextual understanding. It is minimally adequate.

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 has 0% description coverage, so description must compensate. It adds meaning by describing customer_id format ('without hyphens') and providing an example date_range value ('LAST_30_DAYS'). However, it does not list all valid date_range options or constraints, leaving some ambiguity.

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 'Get account-wide conversion summary' with specific verb and resource. However, it does not explicitly differentiate from sibling tools like google_ads_get_conversion_performance or google_ads_account_performance, which also deal with conversions or summaries.

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?

No guidance on when to use this tool versus alternatives such as google_ads_get_conversion_performance or google_ads_campaign_performance. The description lacks context for when an account-wide summary is preferred over more granular reports.

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