google_ads_keywords_list

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

No annotations exist, but the description declares read-only and lists returned fields. While it omits pagination or rate limits, the read-only nature and field list provide adequate transparency 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 concise sentences covering action, parameters, return fields, read-only status, usage, and alternative. Front-loaded with key information; no filler.

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, usage, return fields, and read-only nature. Lacks details on pagination or sort order, but given the tool's simplicity and optional parameters, the description is mostly 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 coverage is 100%, and the description adds a constraint (customer_id optional fallback, campaign_id and ad_group_id must agree when both supplied) not in schema. This adds meaning beyond the parameter descriptions.

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 lists keyword criteria, scoped optionally to campaign/ad group and filtered by status. It distinguishes itself from siblings like google_ads_keywords_diagnose and explicitly connects to pause/remove operations.

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 tells when to use (locate criterion_id before pause/remove, audit coverage) and when not (quality-score diagnostics should use google_ads_keywords_diagnose). Provides clear context and alternatives.

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