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 behavioral disclosure burden. The verb 'Lists' conveys read-only semantics and the phrase 'optionally filtered by account' discloses the filter behavior, but pagination behavior (indicated by pageSize/pageToken parameters), auth requirements, and response shape are not mentioned. It covers the essential safety-relevant trait but leaves operational details undisclosed.

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, front-loaded sentence with zero waste. The action verb leads, the resource follows, and the optional filter is stated in six words. 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?

For a straightforward list operation, the core purpose and filter option are complete. However, with no annotations, no output schema, and 0% parameter coverage, the description leaves pagination mechanics (how pageSize and pageToken relate) to inference from parameter names, and says nothing about the response's list format or whether property metadata is nested. Adequate but with a clear 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?

Schema description coverage is 0%, so the description must compensate for all three parameters. It adds meaning only to accountId via 'optionally filtered by account'; pageSize and pageToken receive no explanation of how they interact (e.g., pageToken being returned from a prior page). The description partially compensates for the coverage gap but leaves two of three parameters semantically under-documented.

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 (Lists), a precise resource (GA4 properties), and the scope (all, optionally filtered by account). This cleanly distinguishes it from sibling tools like ga4_get_property (single property fetch) and ga4_list_accounts (account-level enumeration), so an agent can select it confidently without opening the schema.

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 statement implies the usage context: call this when you need to enumerate GA4 properties, optionally scoped to an account. However, it provides no explicit when-to-use/when-not-to-use guidance and names no alternatives, leaving the agent to infer routing from sibling names alone.

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