google_ads_keywords_diagnose

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

The description declares the tool is read-only, but with no annotations, it should cover more behavioral aspects such as required permissions, rate limits, or data freshness. It does provide remediation hints, which adds value.

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?

Two sentences efficiently convey purpose, output, and usage guidance. Every sentence adds value, and information is front-loaded.

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?

Despite no output schema, the description lists severity groups and returned fields (criterion_id, text, ad_group_id, remediation hint). For a diagnostic tool with 2 parameters and full schema coverage, this is complete.

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 description coverage is 100%, so the schema already documents customer_id and campaign_id well. The description adds context that campaign_id runs across all ad groups, enhancing understanding.

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 quality-score and delivery-status issues for keywords in a campaign, specifying the output grouped by severity with fields. It distinguishes from sibling tools like google_ads_keywords_list and google_ads_keywords_suggest.

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 advises using this tool before pulling raw search-terms reports, providing clear usage context. However, it does not explicitly exclude other scenarios or mention alternatives like google_ads_campaigns_diagnose.

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