ga4_list_accounts

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

With no annotations provided, the description carries the full behavioral disclosure burden. It explicitly states the tool is read-only, auto-paginated, and scoped to authenticated user access, which are key behavioral traits. It stops short of describing response shape or potential limitations, but covers the most important safety and execution behavior.

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, well-structured sentence with no filler. Key facts—action, resource, scope, read-only safety, and pagination—are front-loaded and each 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 simple, single-parameter, read-only listing tool, the description plus schema is nearly sufficient to invoke correctly. It discloses authentication, safety, and pagination; the only real gap is the lack of an explicit response shape, which 'list' strongly implies and no output schema exists to confirm.

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 one parameter, pageSize, with zero description coverage, and the description does not mention it directly. 'Auto-paginated' subtly hints at pagination, but the description fails to explain how pageSize affects behavior; it relies entirely on the parameter name and schema constraints.

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?

Uses a specific verb 'List' with the resource 'raw GA4 Analytics Admin accounts', clearly identifying the object and scope. The phrase 'accessible to the authenticated user' sharpens the definition and separates it from sibling tools like ga4_list_properties.

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 the usage context: call this when listing GA4 admin accounts for the current authenticated user. However, it offers no explicit guidance on when to prefer this over related tools such as ga4_list_properties or ga4_list_admin_resources, and it does not state when not to use it.

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