Retrieves the custom Core Reporting dimensions and metrics for a specific property

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

With no annotations provided, the description must carry the full burden of behavioral disclosure. It only states that the tool returns custom dimensions and metrics, but does not mention any side effects, authentication requirements, rate limits, or whether the operation is read-only. For a simple read operation, this is minimally acceptable but lacking.

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 short and front-loaded with the main purpose. It includes an 'Args' section for the parameter. However, it could be slightly more compact or structured, but it is efficient and avoids unnecessary 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 tool is simple with one required parameter and an output schema exists, the description adequately covers the parameter format. However, it does not mention what the output contains (e.g., a list of objects) or any prerequisites, though the output schema may cover return values. It is minimally complete but leaves some context unexplored.

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 schema coverage is 0%, meaning the schema itself provides no description for property_id. The description compensates by explaining accepted formats (number or 'properties/' string), which adds meaning beyond the schema's type definition.

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 title and description clearly state the tool retrieves custom dimensions and metrics for a specific property. It uses a specific verb ('returns') and resource ('custom dimensions and metrics'), and it is easily distinguished from sibling tools like get_account_summaries or run_reports.

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 is provided on when to use this tool versus alternatives. For example, it does not explain how it differs from get_property_details or when a user should choose this over other tools. The description only states what it does without context.

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