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 this is a read-only listing operation and identifies which properties are included (those accessible with current credentials), plus the returned fields. However, it does not mention pagination, rate limits, result ordering, whether archived properties are included, or error behavior.

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 two concise sentences with no filler. The first sentence front-loads purpose and scope; the second lists the return fields. Every sentence 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 zero-parameter, read-only listing tool with no output schema, the description is nearly complete: it states what the tool returns and what properties are included. The only minor gap is lack of information about pagination or result limits, but the core invocation is fully specified.

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 baseline is 4 and the description need not explain parameter behavior. There is no parameter information to add beyond the empty schema, and the description appropriately focuses on output and scope instead.

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 action ('List'), a specific resource ('GA4 properties'), and a clear scope ('accessible with the current credentials'). It also enumerates the returned fields, clearly distinguishing this property-listing tool from siblings that list accounts, admin resources, or audience exports.

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 description makes the tool's context clear: call it to list all GA4 properties the credentials can access, with the expected return fields listed. It does not explicitly name alternative tools or exclusion criteria, but 'GA4 properties' and 'List all' provide solid guidance for selecting this tool over siblings.

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