ga4_list_account_summaries

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

The annotations already mark this as read-only and open-world, but the description goes further by explaining the access boundary (explicit email grant required) and showing the exact response shape. It adds meaningful behavioral context beyond the structured annotations without contradicting them.

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, well-organized, and every sentence earns its place: the main purpose, the when-to-call guidance, the access caveat, and the response format. The response example is useful and not padded with irrelevant detail.

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 zero-parameter discovery tool, the description is fully complete. It explains what the tool returns, how the response is structured, the access model, and how it fits into the workflow. Nothing needed for correct invocation is missing.

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 tool accepts zero parameters, so there is nothing for the description to explain about parameter meaning. The baseline for zero-parameter tools is 4, and the description appropriately focuses instead on the response shape, which is the semantically relevant part here.

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 verb ('List') and a specific resource ('every GA4 account and its child properties accessible to this service account'). It clearly positions itself as a discovery tool for finding property_id values, which distinguishes it from the property-scoped sibling list tools like ga4_list_custom_metrics and ga4_list_data_streams.

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?

Explicitly instructs 'CALL THIS FIRST' and explains the purpose: to discover which property_id to pass into other tools. It also provides a crucial constraint: the service account only sees accounts/properties where its email has been explicitly added. This is strong, actionable usage guidance.

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