google_ads_keywords_suggest

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

The description discloses it is read-only and does not add anything to the account. However, no annotations are provided, so the description carries full burden. It lacks details on rate limits, authentication, or response pagination, but the read-only nature is clearly communicated.

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?

The description is three sentences: first states purpose, second lists return fields, third clarifies read-only and sibling tool. Every sentence adds value, and it is front-loaded with the main action.

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?

Given the moderate complexity (4 params, no output schema), the description compensates well by listing return fields and clarifying defaults. However, it could mention that results may be empty or limited, and no error handling is described. Overall, it is nearly complete for agent use.

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%, and the description adds valuable context: seed_keywords are 1-20 terms treated as topic anchors, language_id defaults to Japanese with common examples, geo_id defaults to Japan with common examples, and customer_id is optional with fallback to credentials.

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 it generates new keyword ideas from seed terms using the Google Ads Keyword Planner API, lists the output fields, and distinguishes from the sibling tool 'google_ads_keywords_add' by directing to use that for materializing ideas.

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 states it is read-only and does not modify the account, and advises using 'google_ads_keywords_add' to add keywords. This provides clear when-to-use and when-not-to-use guidance.

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