Get analytics overview time series

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

No annotations are provided, so the description must disclose behavior. It mentions the metrics (sessions, pageviews, etc.) and bucket breakdown, but does not state that the operation is read-only, discuss rate limits, or describe the output format. The safety profile is implied but not explicit.

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 sentences, no redundant words. The first sentence states purpose and relation to sibling, the second gives practical usage advice. Information is front-loaded and 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?

The description explains the tool's output conceptually (same metrics as overview in time buckets) and provides bucket size recommendations. However, it lacks details on the output structure (e.g., fields per bucket, pagination). Given no output schema, this is a minor gap but not critical for correct invocation.

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 description coverage is 100%, so parameters are already documented. The description adds value by recommending bucket size for different ranges, which is not in the schema enum description. This guidance helps the agent choose appropriately.

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 retrieves the same metrics as rybbit_get_overview but broken into time buckets for charting trends. It differentiates from siblings by specifying the time-series aspect, and the sibling list includes rybbit_get_overview as the non-time-series version.

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 description provides explicit guidance on choosing bucket size based on time range (e.g., 'minute' for last hour, 'day' for weeks/months). It implies use cases for trends but does not explicitly state when not to use this tool.

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