ga4 get metadata

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the description does not need to cover side effects. It adds only moderate context beyond that, such as the 'complete list' scope, but does not mention response limits, pagination, or property prerequisites.

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?

Two short sentences with the main action and scope front-loaded, followed by a concrete use case. There is no redundant or filler language.

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 metadata-listing tool with one fully documented parameter, an output schema, and complete safety annotations, the description is largely sufficient. It loses a point because the boundary with ga4_get_custom_definitions is unclear, which could lead an agent to select the wrong sibling tool.

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 fully describes propertyId with type and an example, so the description need not repeat parameter details. It adds no significant semantic nuance beyond 'specific GA4 property', so the baseline 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?

States a specific verb ('Get'), resource ('complete list of dimensions and metrics'), and target ('specific GA4 property'). It is clear and actionable, but it does not explicitly contrast with ga4_get_custom_definitions or the report tools, which also deal with dimensions/metrics, so sibling differentiation is only partial.

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?

Provides a practical use case ('Useful for discovering custom dimensions/metrics'), which implies a discovery context. However, it gives no explicit when-to-use vs. alternatives, especially ga4_get_custom_definitions, and no exclusions or conditions for choosing another tool.

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