google_ads_keywords_list

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

Description declares it is read-only and lists return fields, which is helpful given no annotations. However, it does not mention pagination, rate limits, or data freshness, which would be useful for a list tool.

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?

Four sentences: purpose, return fields, read-only note, usage guidance. No fluff, front-loaded, each sentence adds value.

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?

Covers purpose, scope, return values (important since no output schema), and alternative tools. Missing pagination/limit details but otherwise thorough for a list 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 covers all parameters with descriptions (100% coverage). Description paraphrases scoping and filtering but adds no new meaning beyond the schema, so baseline of 3 is appropriate.

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?

Description clearly states the tool lists keyword criteria, optionally scoped by campaign/ad group and filtered by status. It distinguishes from siblings by explicitly mentioning usage to locate criterion_id before pause/remove and directing to keywords_diagnose for quality score.

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 to locate a criterion_id before calling keywords.pause / remove, or to audit keyword coverage' and 'For quality-score diagnostics use google_ads_keywords_diagnose'. This tells the agent when and when not to use the tool.

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