ga4_list_custom_dimensions

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the read-like action 'Lists' but does not disclose pagination behavior despite pageSize and pageToken existing in the schema, nor does it describe response shape or any access requirements. This leaves meaningful behavioral context unstated.

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 sentence with no redundant words, front-loading the operation and resource. It is appropriately sized for a straightforward list operation and every word contributes meaning.

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 tool with no annotations, no output schema, and a schema description covering only one of three parameters, the description is too terse. It omits pagination semantics, return value expectations, and any guidance about how to use pageToken or pageSize. An agent would need to infer important call details.

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 only 33%: only propertyId has a description. The description adds only the general context that dimensions are 'defined for a GA4 property', which indirectly reinforces propertyId's role, but it says nothing about pageSize or pageToken semantics. With low schema coverage, the description should compensate, and it does not adequately do so.

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 ('Lists') and resource ('custom dimensions defined for a GA4 property'), which clearly identifies the operation. It distinguishes itself from the sibling ga4_list_custom_metrics by naming a different resource type, so an agent can select it 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 context is implied: use this when you need the custom dimensions for a GA4 property. However, it provides no explicit guidance about when to prefer this over alternatives such as ga4_list_custom_metrics or other GA4 listing tools, and it does not mention pagination as a usage consideration.

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