ga4 list accounts

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

Annotations already cover the safety profile (readOnlyHint, idempotentHint, openWorldHint, destructiveHint=false). The description adds genuine behavioral context beyond annotations: auto-pagination behavior ('auto-paginated') and the raw/unprocessed nature of the data returned, plus the user-scoping constraint. No contradiction with annotations.

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?

A single sentence packs the verb, resource, scope, safety posture, and pagination behavior into one front-loaded clause with parenthetical extras. There is zero filler and every element earns its place.

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 low-complexity tool with one optional, fully documented parameteraint — and an output schema that relieves the description of explaining return values — the description is complete. An agent knows what it returns, for whom, and how pagination behaves.

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% — the pageSize parameter is fully documented with default, bounds, and pagination guidance, so the description needs to add little. 'Auto-paginated' weakly reinforces the schema's pagination note but adds no new parameter-level meaning; the baseline 3 applies.

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 names a specific verb ('List'), a precise resource ('raw GA4 Analytics Admin accounts'), and a scope ('accessible to the authenticated user'). It clearly differentiates from siblings like ga4_list_properties and ga4_list_admin_resources by specifying the account level, and 'raw' further disambiguates from processed/report-style 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 implies when to use the tool — as a read-only listing of accounts for the current user — and names no prerequisites beyond authentication. However, it never explicitly contrasts with any sibling list tool (e.g., ga4_list_properties, ga4_list_admin_resources) or states when not to use it, so routing among the many list-style siblings is left to inference.

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