google_ads_health_check_all

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

No annotations provided, so description carries full burden. It declares 'Read-only' and explicitly describes the output structure including limits (up to 5 detailed diagnostics) and field breakdown, ensuring full transparency.

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 detailed but well-structured, front-loading the primary purpose and then listing returns in a compact notation. Slightly verbose due to full output description, but each sentence earns its place.

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 the complexity of a health check across all campaigns with diagnostics, the description covers input, behavior, output format (including nested fields), and distinguishes from related tools. No output schema exists, so description compensates fully.

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% for the single optional parameter. The description adds value by explaining fallback behavior to configured credentials when omitted, which aids correct invocation.

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 'Screen every campaign... and run detailed delivery diagnostics on up to 5 problem/warning campaigns' with specific verbs and resource scope. It also distinguishes from siblings like 'google_ads_campaigns_diagnose' and 'google_ads_monitoring_cpa_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?

Explicitly instructs when to use this tool for overall account health check and provides alternative tools for single-campaign diagnosis and CPA-goal monitoring, offering clear usage boundaries.

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