search_google_ads

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

Discloses that it runs a remote scraper with a 30-second to few-minute duration, saves full results to a JSON file, and returns only a compact preview inline. These details go beyond the readOnlyHint and openWorldHint annotations, providing valuable behavioral context for an agent.

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, each serving a distinct purpose: stating the action and output, explaining the process and time, and directing to a related tool for full results. It is front-loaded and contains no superfluous text.

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 tool's complexity (6 parameters, 1 required, output schema present), the description covers the essential behavior, timing, data handling, and provides a pointer to related tools. It does not detail every parameter, but the schema handles that, making the description sufficient for an agent to select this 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 coverage is 100%, so the baseline is 3. The description mentions searching 'by advertiser name or domain,' which aligns with the advertisers parameter description but does not add new semantic information beyond what the schema already provides.

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 searches the Google Ads Transparency Center for live ads by advertiser name or domain, and lists the returned fields (headlines, formats, etc.). It distinguishes from sibling tools like search_facebook_ads (different platform) and read_saved_results (for full data), leaving no ambiguity.

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 to use read_saved_results for paging through full data, and mentions the remote scraper takes 30s–few minutes, setting expectations. However, it does not explicitly state when not to use this tool versus alternatives like start_google_ads_scrape, though the contrast is implied.

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