ga4_get_audience_export_diagnostics

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

The description explicitly says 'Read-only', which is the key behavioral trait for an agent deciding whether invocation is safe. It also lists what operations will be performed. It does not discuss rate limits, pagination, or error behavior, but for a non-mutating diagnostic tool the disclosed behavior is largely sufficient.

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 compact, front-loads the critical read-only qualifier, and enumerates the three operations in a single breath. Every clause adds meaningful information, with no redundant restatement of the tool name.

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?

With no output schema, the description still conveys what the caller will get: a list of exports, state counts, and optional row samples. It is somewhat light on details like how an existing export is selected for sampling or what 'state counts' contains, but for a read-only diagnostic of this complexity it is reasonably 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 coverage is 67%, and the description adds only one parameter-level insight: 'optionally samples rows' maps to includeRowSample. propertyId is already documented in the schema, while pageSize and sampleLimit have constraints but no descriptions in either the schema or the tool description. This matches the baseline for moderate schema coverage.

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 identifies the resource (Audience Export) and the specific operations: listing exports, reporting state counts, and optionally sampling rows. It does not explicitly distinguish itself from closely related sibling tools like ga4_list_audience_exports or ga4_query_audience_export, so it stops short of a 5.

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 word 'diagnostics' implies a troubleshooting/health-check use case, and the read-only framing suggests safe inspection. However, there is no explicit statement of when to use this tool versus overlapping siblings, nor any exclusions or alternative routing guidance.

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