ghl_ad_google_keyword_ideas_get

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

The annotation readOnlyHint is false, but the description states OAuth scopes 'adPublishing.readonly', implying read-only behavior. This is a direct contradiction. The description also does not disclose important traits like pagination or rate limits beyond what annotations fail to indicate.

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 relatively concise, with the main purpose in the first sentence. Extra endpoint and scope details are useful but could be trimmed. Still effective.

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?

Missing important context: no output schema so return format is unspecified, no usage context (e.g., when to use vs other Google Ads tools), and the contradiction undermines trust. Incomplete for an agent rely solely on this definition.

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%, so the schema already describes all parameters. The description adds no additional meaning beyond the schema, warranting a baseline score of 3.

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 retrieves keyword ideas for Google Ads campaigns, with a specific verb ('Get') and resource ('keyword ideas'). It differentiates from sibling tools like campaign or account tools.

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 explains it retrieves keyword suggestions, but does not provide explicit guidance on when to use this tool versus alternatives (e.g., targeting search tools). No exclusions or context are given.

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