analytics_time_series

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions the type of data returned (rolling averages, seasonality, forecast) but omits important details like authentication requirements, rate limits, or data constraints. The description is insufficient for a tool with multiple parameters and no annotation support.

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 two concise sentences, each adding value. The first explains the core outputs, the second lists supported analysis features. No wasted 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's complexity (10 parameters, no output schema, no annotations, many siblings), the description provides a high-level overview but lacks details on how parameters interact (e.g., days vs. startDate/endDate, window size relationship). It also does not explain the return format. However, the schema descriptions fill some gaps, making the description adequate but not complete.

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?

All 10 parameters have descriptions in the schema (100% coverage), so the baseline is 3. The description mentions 'multi-dimensional analysis, metrics selection, and custom granularities,' which maps to parameters but adds no new meaning 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 clearly states 'Get advanced time series data including rolling averages, seasonality strength, and trend forecasting,' which specifies the exact capabilities and distinguishes it from simpler siblings like analytics_trends or analytics_anomalies.

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 advanced time series analysis but does not explicitly state when to use this tool versus other analytics tools like analytics_trends or bing_analytics_time_series. No exclusions or alternatives are mentioned.

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