list_custom_dimensions

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

Since no annotations are provided, the description carries the full burden of behavioral disclosure. It does not mention read-only behavior, pagination, inclusion of archived dimensions, required permissions, or any other behavioral trait. This is minimal for a list operation.

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, concise sentence that is front-loaded and contains no unnecessary words. It is appropriately sized for the simple operation it describes.

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?

The output schema likely covers return values, so that absence is not a major issue. However, the description lacks important context such as pagination behavior, whether archived dimensions are included, and any permission requirements. For a simple list tool, this is a moderate gap but not severely incomplete.

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 0% description coverage, and the description adds little beyond the property_id name. It only indirectly implies the parameter via 'GA4 property,' but does not explain the ID format, where to obtain it, or any other usage detail, leaving the agent with insufficient parameter guidance.

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 action verb ('List') and a specific resource ('custom dimensions') scoped to a GA4 property. This clearly distinguishes it from sibling tools like list_custom_metrics, create_custom_dimension, and archive_custom_dimension.

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 provides no explicit guidance on when to use this tool versus alternatives. There is no mention of list_custom_metrics, create_custom_dimension, or any conditional context, leaving usage to be inferred only from the tool name.

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