ga4_list_properties

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

No annotations are provided, so the description carries the full burden. It discloses that results are limited to what 'the credentials' can see, implying authentication scoping, but it does not specify the return format beyond 'summaries,' whether pagination applies, or whether it returns both accounts and properties in a single call. Behavior is only partially transparent.

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, clear sentence with no filler. The essential scope (accounts and property summaries) is front-loaded and the credential constraint is included. Every word 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?

Without an output schema, the description should clarify what the agent can expect. It says 'summaries' but not whether each item includes a property ID, account hierarchy, or how to map them to sibling tool parameters. For a discovery tool that feeds into other GA4 tools, this missing linkage is a notable gap.

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 has zero parameters, so the schema is fully covered. A baseline of 4 applies because there are no parameters to explain. The description adds no parameter-specific details, but none are needed.

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 clear action (list) and resource (GA4 accounts and property summaries). It distinguishes itself from sibling report tools like ga4_run_report, ga4_top_pages, and gsc_* tools, which operate on specific properties rather than enumerate them.

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 purpose implies usage for discovery before report tools, but the description does not explicitly state when to use it versus siblings. It lacks guidance like 'use this to get property IDs before calling ga4_run_report' or exclusions such as 'use gsc_list_sites for Search Console.' Useful context 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.