google_ads_health_check

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

With no annotations provided, the description carries the full burden. It explicitly discloses that the operation is read-only and that secrets are never returned, and it explains what is verified. It stops short of describing output format or potential rate-limit impacts, but the key behavioral traits are covered.

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 a single sentence of about 20 words, immediately leading with 'Read-only connectivity check.' Every phrase adds information, with no filler or repetition.

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?

For a parameterless health-check tool with no output schema, the description adequately explains the tool's role and the dimensions it validates. It hints at the output via 'actionable warnings' and explicitly notes that secrets are not included, which is sufficient for safe invocation.

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?

The tool has zero parameters, and the empty input schema confirms this. A baseline of 4 applies for 0-parameter tools, and the description still provides meaningful context by clarifying the operation is a check that yields warnings rather than a mutation.

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 states a specific verb ('Verifies') and resource ('connectivity') for Google Ads, and enumerates the exact aspects checked: credential presence, API access, login customer visibility, API version, and warnings. This clearly distinguishes it from sibling data-retrieval tools.

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 phrase 'Read-only connectivity check' provides clear context for when to invoke this tool, especially before other Google Ads operations. It does not explicitly name alternatives or exclusions, but the tool's distinct health-check purpose is evident from the description alone.

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