list_custom_dimensions

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

With no annotations, the description bears the full burden. The verb 'List' clearly indicates a read-only operation, but it does not disclose whether archived dimensions are included, pagination behavior, or any required permissions. This leaves some behavioral aspects undefined.

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, front-loaded sentence with no redundant words. It efficiently conveys the tool's core purpose in eight words.

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?

Given the low complexity (one parameter), the presence of an output schema, and no annotations, the description adequately covers the essential purpose and scope. However, it omits potential behavioral nuances like whether archived custom dimensions are returned, leaving minor ambiguity for the agent.

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. It clarifies that property_id refers to a GA4 property, adding context beyond the schema's bare 'Property Id', but it does not explain expected formats or additional constraints for the parameter.

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 ('List'), identifies the resource ('custom dimensions'), and scopes it to 'a GA4 property', distinguishing it from sibling tools like list_custom_metrics. This clearly conveys what the tool does without ambiguity.

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?

No explicit guidance is given on when to use this tool versus alternatives like list_custom_metrics or how it relates to create_custom_dimension and archive_custom_dimension. The purpose implies usage when retrieval of custom dimensions is needed, but this is not stated.

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