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?

No annotations provided, and the description only says 'Returns' without detailing read-only nature, authentication requirements, rate limits, or other behavioral aspects. The agent has limited insight into side effects or constraints.

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 very concise and front-loaded with the main purpose. The use of a structured Args section is clear. However, it could be slightly more succinct by removing the 'Args:' header and integrating the parameter description.

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 simplicity of the tool (one parameter, output schema present), the description is minimally adequate. It explains the purpose and parameter format. However, it lacks context about the response structure, which is partially covered by the output schema.

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 description adds meaningful context for the single parameter property_id, specifying accepted formats (number or string with 'properties/' prefix). This goes beyond the schema's anyOf type definition, which only defines type as integer/string.

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 it returns custom dimensions and metrics for a property. It distinguishes the tool's purpose from sibling tools like run_report or get_account_summaries, but does not explicitly differentiate them.

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. For example, it does not mention that this tool is for custom dimensions/metrics while run_report is for standard reporting.

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