get_metadata

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

No annotations are provided, so the description carries the full burden. It only states that the tool 'lists' data, without disclosing any behavioral traits such as whether it returns both standard and custom dimensions/metrics, data freshness, permissions required, or pagination behavior. This is minimal disclosure.

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 two short sentences, both highly relevant and free of filler. The first sentence states the core function, and the second adds practical context. Every word earns its place.

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 tool's simplicity (single parameter, output schema present), the description covers the essential purpose and usage. However, it could mention that the listing includes both standard and custom dimensions/metrics, which would improve completeness. The output schema likely documents return values, so that's not required.

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 one required parameter (property_id) with 0% schema description coverage, meaning no description in the schema. The tool description does not add any explanation for this parameter beyond its name. For a critical parameter like property_id, the description should clarify its format or meaning, but it does not.

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 clearly states the tool lists all available dimensions and metrics for a GA4 property, using the verb 'list' and specifying the resource. It distinguishes from siblings like run_report by positioning this as a discovery tool to get names for use in run_report.

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 second sentence explicitly says 'useful to discover which dimension/metric names you can use in run_report,' providing clear context for when to use this tool. However, it does not mention alternatives or when not to use it, which is a minor omission.

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