gads_keyword_performance

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

With no annotations, the description provides defaults and filters but lacks disclosure of read-only nature, rate limits, or behavior when no filters are applied. Adequate but not comprehensive.

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, front-loaded with key information, 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?

Without an output schema, the description lists metrics but does not explain return structure or pagination. Adequate for basic usage but leaves gaps for a tool with 7 parameters.

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 description adds meaning to defaults (last 28 days, enabled keywords) and mentions filter parameters, but with 29% schema coverage, it does not fully compensate for undocumented params like limit or customer_id.

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 'Keyword-level performance' and lists specific metrics (match type, quality score, clicks, cost, conversions), distinguishing it from sibling tools like gads_campaign_performance or gads_ad_group_performance.

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 mentions filtering by campaign_id or ad_group_id and defaults, but does not explicitly guide when to use this vs alternatives (e.g., gads_search_terms_report) or when not to use it.

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