ga4_list_accounts

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

With no annotations provided, the description carries the disclosure burden. 'Lists' implies a read-only operation and the scope is stated, but there is no mention of pagination behavior, response structure, or any rate-limit considerations. The behavior is safe and predictable but not richly described.

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 sentence with no filler. The key verb, resource, and scope are front-loaded, making it immediately actionable for an agent.

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 simple list tool with no required parameters, the description covers the core purpose. However, the absence of an output schema and the lack of any mention of pagination means the agent is left to infer how to retrieve all accounts, especially when using pageSize and pageToken.

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 0%, and the description does not mention pageSize or pageToken at all. While those parameter names are fairly self-explanatory and the schema provides min/max constraints, the description adds no semantic value about pagination or how these parameters affect the returned account list.

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 uses a specific verb 'Lists' and identifies the exact resource: all Google Analytics 4 accounts accessible to the authenticated user. This clearly distinguishes it from ga4_get_account, ga4_list_properties, and similar list tools for other systems like GTM or GBP.

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 when an agent needs to enumerate GA4 accounts, and the authentication context is helpful. However, it does not explicitly mention when to prefer ga4_get_account for a single account or explain how pagination should be handled when iterating over all accounts.

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