List GA4 custom dimensions

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds useful behavioral context: it returns parameter name, display name, and scope, and it is read-only. It doesn't mention pagination behavior, but the schema already documents pageToken and nextPageToken, so the description doesn't need to repeat it.

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?

Two sentences with no fluff. The core purpose is front-loaded, the returned fields are listed, and the use case is stated. 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 read-only list tool with full schema coverage and safety annotations, the description is nearly complete. It could mention that the response is paginated, but the schema already covers pageToken and nextPageToken. The only minor gap is not describing the response shape, but no output schema exists and the description lists the key fields returned.

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 100%, so the schema already documents all three parameters. The description adds the note that propertyId can be discovered via ga4_list_account_summaries, which is helpful, but it doesn't add much beyond the schema. Baseline 3 is appropriate.

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 ('Lists'), a specific resource ('custom dimensions configured on a GA4 property'), and the key fields returned (parameter name, display name, scope). It also distinguishes itself from ga4_run_report by noting it's useful before referencing dimensions in that tool. This is a clear, specific purpose that an agent can act on.

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 says it's useful for discovering which custom dimensions exist before referencing them in ga4_run_report, which gives a clear when-to-use context. It doesn't explicitly say when not to use it or name alternatives like ga4_get_metadata, but the context is sufficient for most cases.

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