wafle_exports_google_ads

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

Annotations already declare readOnlyHint and idempotentHint, covering safety. The description adds useful behavioral context by specifying that email/phone are hashed and that output uses Google's expected column names. This goes beyond the annotations, though it does not describe pagination or output format details.

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 a single, front-loaded sentence that immediately communicates the tool's purpose and formatting specifics. Every word adds value without redundancy.

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?

The description covers the core purpose and key formatting details, but it omits information about the optional parameters, return format, and any prerequisites or constraints. For a relatively simple export tool with no output schema, this is adequate but not fully 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 description coverage is only 33%, with segment and since_ts lacking descriptions. The tool description does not explain these optional parameters or how they affect the export. It only indirectly relates via 'audience' but fails to compensate for the missing parameter semantics.

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 exports an audience formatted for Google Ads Customer Match, specifically mentioning hashed email/phone and Google-expected column names. This distinguishes it from sibling export tools like wafle_exports_customers and wafle_exports_meta_audience by naming the target platform and format.

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?

Usage context is implied through the Google Ads Customer Match mention, but there is no explicit guidance on when to choose this tool over alternatives such as wafle_exports_meta_audience. No when-not-to-use or alternative tool names are provided.

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