get_custom_dimensions_and_metrics

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

With no annotations provided, the description only states 'Retrieves' implying a read operation, but lacks details on behavioral traits like data limits, permissions required, or whether the response is paginated. Minimal transparency beyond the basic 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?

Single sentence that is clear and to the point. No extraneous information, every word adds value.

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 simple one-parameter input and no output schema, the description adequately covers the purpose but could mention what the response contains (e.g., list of custom dimension/metric objects). Adequate but not comprehensive.

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 coverage is 100% (only property_id), and the description repeats the parameter description verbatim ('GA4 property ID') without adding new semantic context. Baseline score of 3 is appropriate.

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?

Description clearly states the verb 'Retrieves' and the specific resources 'custom dimensions and custom metrics' for a GA4 property. It distinguishes from sibling tools like run_report and get_property_details by its unique focus on custom dimensions/metrics.

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 guidance on when to use this tool versus alternatives such as get_property_details or run_report. The description does not mention circumstances where this tool is preferred or when not to use it.

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