Ga4.Admin.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 disclosure burden, yet it says nothing about authentication scope, pagination behavior, or the fact that this is a read-only Admin API call. The presence of an output schema covers return values, but the operational behavior of the call remains 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?

One short sentence, front-loaded with the verb and resource, with no filler. It may be slightly too terse for a tool with zero annotation coverage, but there is no wasted text.

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?

An output schema exists, so return values need not be explained, and the single-parameter surface is simple. However, with no annotations and no mention of pagination, auth, or ID format, the definition leaves the agent to guess at call mechanics for an Admin API tool.

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% and the single parameter account_id is a bare string in the schema; the description's phrase 'under an Admin account' does tie the parameter to the GA4 Admin account resource, adding modest meaning. It does not say what format the ID takes (numeric vs. 'accounts/123') or where to source it, so it only partially compensates for the coverage gap.

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?

States a specific verb ('List') and resource ('GA4 properties') scoped to an Admin account, which is unambiguous about what the tool returns. It does not distinguish itself from siblings like ga4.admin.list_data_streams or ga4.admin.list_key_events, but the resource named is distinct enough that an agent can select it without confusion.

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?

There is no guidance on when to use this versus ga4.admin.list_data_streams, ga4.admin.list_key_events, or ga4.report — the agent must infer from the tool name alone. No prerequisites, no note that an account_id must first be obtained (e.g., via a GA4 account listing).

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