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 only states the action ('List') but does not disclose read-only behavior, pagination, whether archived custom dimensions are included, or what happens when property_id is omitted. The description is not misleading but leaves important behavior unspecified.

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 a single clear sentence with no filler and the verb is front-loaded. It is concise, though it achieves this by omitting contextual details that other dimensions penalize.

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 simple list operation with only one optional parameter and an output schema, the description is minimally viable: it names the resource and scope. However, with no annotations, no usage guidance, and no parameter explanation, there are clear gaps for an agent trying to call it correctly without prior GA4 knowledge.

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 by explaining the property_id parameter. However, it only says 'on a property' and does not clarify the expected format (e.g., numeric GA4 property ID), whether the parameter is effectively required despite being optional, or what the default null means. The schema title alone carries most of the meaning.

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 names a specific verb ('List'), a specific resource ('custom dimensions'), and a clear scope ('on a property'). This distinguishes it from sibling tools like ga4_create_custom_dimension, ga4_archive_custom_dimension, and ga4_list_custom_metrics without needing to open 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?

There is no guidance about when to use this tool versus ga4_list_custom_metrics or ga4_list_properties. The description does not mention prerequisites, such as obtaining a property_id from ga4_list_properties, nor does it state any exclusions or alternatives. An agent must infer usage entirely from the tool name and sibling list.

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