Get calls timeseries

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

Annotations already declare readOnlyHint=true, so the agent knows it's safe. The description adds the context that data is grouped by time interval. No contradictions. However, it does not describe what metrics are returned (e.g., call count, duration).

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?

A single, clear sentence with no redundancy. However, it could be structured to include more context without adding length.

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?

With no output schema and 6 parameters, the description is too brief. It does not explain what the timeseries contains (e.g., whether it returns counts, durations, or other metrics), nor does it cover any constraints or date range logic.

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 67% (4 of 6 params have descriptions). The description itself does not mention any parameters or their roles, adding no value beyond the schema.

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 'Retrieve call analytics grouped by a time interval' uses a specific verb ('retrieve'), resource ('call analytics'), and scope ('grouped by a time interval'). It clearly distinguishes from siblings like list_calls (raw list) and get_calls_summary (summary stats).

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 implies usage for retrieving aggregated timeseries data, but does not explicitly state when to use this tool versus alternatives like get_calls_summary or list_calls. No exclusions or prerequisites are mentioned.

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