ga4_list_properties

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

With no annotations provided, the description carries the burden of behavioral disclosure. It explicitly labels the operation as read-only and describes the data returned. This is sufficient for a zero-parameter, non-destructive listing operation, though it does not mention authentication or potential pagination.

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 that front-loads the most important safety characteristic ('Read-only'), followed immediately by the action and resource. Every word contributes meaning; there is no filler or redundancy.

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, no-output-schema list tool, this description is nearly complete. It identifies the resource, the mode, and the key return components. It could be slightly richer by noting the output format or relationship between accounts and properties, but nothing essential is missing for an agent to call it correctly.

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 input schema has zero parameters, so the baseline is 4. The description adds useful output-scope context by listing what will be returned, but there are no parameters for it to explain.

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 ('list'), names the exact resource ('GA4 accounts and their properties'), and even specifies the output elements ('names + ids + measurement streams'). It clearly distinguishes itself from sibling tools like wc_list_accounts and ga4_create_property by scope and operation type.

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 'Read-only' prefix and 'list' verb imply that this is the tool to use for retrieving GA4 account/property information, and the sibling names suggest it is the read counterpart to ga4_create_property. However, it does not explicitly state when to use this tool over alternatives or provide any conditions for selection.

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