google_ads_keywords_diagnose

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

Describes the output structure (groups, fields) and explicitly states 'Read-only'. No annotations were provided, so the description covers behavioral traits adequately.

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?

Three sentences: main function, output detail, usage hint. Front-loaded, efficient, no wasted words.

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?

No output schema, but description clearly explains return format (groups with fields: criterion_id, text, ad_group_id, remediation hint). Covers all necessary context for a diagnostic tool.

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% with descriptions for both parameters. Description adds context about customer_id fallback and campaign_id scope, but schema already does heavy lifting.

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?

Clearly states it reports quality-score and delivery-status issues for keywords in a campaign. Lists specific severity categories and returned fields, distinguishing it from sibling tools like search-terms reports.

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?

Provides explicit guidance: 'Use this before pulling raw search-terms reports; it triages where attention should go.' Implies the tool is for triaging, not raw data.

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