ga4_custom_dimensions_list

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It declares the tool is 'Read-only', which is critical for agent decision-making, and specifies the scope types (EVENT/USER/ITEM). However, it does not disclose potential rate limits, permission requirements, or details about pagination behavior beyond what the schema provides. The transparency is adequate but not extensive.

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 sentence with an appended 'Read-only' indicator. It is front-loaded and contains no unnecessary words. Every part adds value: the verb, resource, output fields, and behavioral note.

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 list tool with a simple input schema and no output schema, the description covers the essential purpose and output fields. It lacks some contextual details such as whether the tool returns all or only active dimensions, or the exact format of the property ID (though the schema covers that). Given the complexity is low and schema is rich, the description is mostly complete but could be strengthened by mentioning the default maxPages value or truncation behavior more explicitly.

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 input schema has 100% description coverage for all three parameters (property, maxPages, pageToken), so the baseline is 3. The description adds no additional semantic information about the parameters; it only mentions the output fields. Thus it does not improve parameter understanding beyond the schema.

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 specifies the verb 'List', the resource 'custom dimensions on a GA4 property', and mentions the output fields (parameter name, display name, scope). This clearly distinguishes it from sibling tools like ga4_custom_metrics_list, which lists metrics instead.

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 states the tool is read-only and lists custom dimensions, which implies it should be used when the agent needs to retrieve dimension metadata. However, it does not explicitly state when not to use it or mention alternatives like ga4_custom_metrics_list for metrics. The clarity is still high, but lacks explicit exclusion conditions.

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