Get metric breakdown

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

Annotations already indicate readOnlyHint=true. The description adds that it returns ranked {x, y} rows and is a top-N breakdown. No contradictions, but lacks details on default limit, pagination, or ordering beyond schema.

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?

Very concise: two sentences that convey core functionality without redundancy. Could benefit from a brief explanation of filter parameters but remains efficient.

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 21 parameters and no explanation of most filters, the description leaves significant gaps. The return format is covered by the output schema, but the agent cannot infer how to use dimensions vs filters. More context is needed for a tool this complex.

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 only 33%, and the description only explains the 'type' parameter (with enum hints) and 'url' as alias. The remaining 18+ parameters (filters like os, browser, etc.) are not explained, leaving the agent to guess their role.

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?

Clearly states it provides a top-N breakdown by a single dimension over a date range, with specific mentions of type=event and url=path. Distinguishes from siblings like get_stats (aggregate) and report_breakdown (multi-dimension), though not explicitly.

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 explicit when-to-use or when-not-to-use guidance. The description hints at usage for custom events and alias but does not differentiate from many sibling tools like get_website_values or report_breakdown.

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