ga4_query_audience_export

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

With no annotations, the description carries the full behavioral burden. It discloses a key behavior: user/device identifiers are redacted by default and require explicit opt-in. This adds meaningful context beyond the schema, though it does not mention pagination behavior or error conditions.

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 two sentences with no filler. The primary action is front-loaded, and the important privacy-related opt-in behavior is stated concisely.

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?

For a query tool with a clear parameter schema, the description covers the core purpose and a critical behavioral constraint. Minor gaps remain around response format and pagination semantics, but the essential information to invoke the tool correctly is present.

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 schema has low description coverage, and the description only adds contextual meaning for includePersonalIdentifiers by explaining the default redaction behavior. It does not elaborate on limit, offset, or audienceExportName, though the parameter names and pattern are reasonably self-explanatory.

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 states a specific action ('Query rows') on a specific resource ('existing GA4 Audience Export'), which clearly distinguishes it from sibling tools like listing exports or running diagnostics.

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 implies usage for fetching row-level data from an audience export, but it does not explicitly state when to choose this tool over alternatives such as ga4_list_audience_exports or ga4_get_audience_export_diagnostics.

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