google_ads_monitoring_zero_conversions

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

No annotations provided, so description carries full burden. It clearly states read-only behavior, hardcoded LAST_7_DAYS window, and that it generates an action plan without executing. Output structure and potential null values are detailed.

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 comprehensive but somewhat dense. It front-loads purpose and lists components, but includes a large output structure that could be summarized. Every sentence serves a purpose, but it could be slightly more concise without losing information.

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?

With no annotations or output schema, the description provides thorough coverage: output structure, hardcoded window, read-only nature, fallback behavior for customer_id, and related tools. It even mentions edge cases (null search_term_quality when clicks==0).

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 context beyond schema: customer_id falls back to configured credentials, and campaign_id can be obtained via google_ads_campaigns_list. This adds moderate value.

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 diagnoses a Google Ads campaign not acquiring conversions, specifying it composes tracking config, bidding alignment, funnel, delivery diagnostics, and search-term quality. It explicitly distinguishes from sibling tools like google_ads_monitoring_cpa_goal and google_ads_monitoring_cv_goal.

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?

The description explicitly says 'Read-only; generates an action plan but does not execute anything.' It also directs when to use alternatives: 'For CPA monitoring use google_ads_monitoring_cpa_goal; for CV-count monitoring use google_ads_monitoring_cv_goal.'

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