ga4_list_accounts

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

The description conveys that the operation is read-only and scoped to the authenticated user, which are useful behavioral cues in the absence of annotations. However, it does not disclose pagination, error behavior, or whether account and property summaries are returned together.

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?

One sentence, front-loaded with the core action and resource, with no filler words. It is appropriately sized for the tool's simplicity.

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 read-only listing tool with only optional auth parameters, the description is nearly sufficient. It does not define return structure or pagination, but 'summaries' gives a reasonable expectation of what will be returned.

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?

Both parameters lack schema descriptions (0% coverage), and the description never mentions connection_id or session_token. The parameter names are somewhat self-explanatory, but the description adds no meaning about how they are used.

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 (List), a specific resource (GA4 account/property summaries), and a scope qualifier ('accessible to the connected Google user'). This clearly differentiates it from the GTM siblings, which target a different Google product.

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 gives no guidance about when to call this tool versus alternatives such as ga4_get_property or gtm_list_accounts. The 'connected Google user' phrasing implies authentication context, but no exclusion criteria or fallback routing is provided.

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