pbi_create_rolling_average_measure

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

No annotations provided. Description only shows a DAX template but doesn't disclose behavior such as overwrite effects, naming, permissions, or side effects. The template gives some insight but insufficient.

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?

Description is short and includes a code block for the DAX template. It is front-loaded with the purpose. Could be slightly improved by adding structure or brief notes on parameters.

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 10 parameters with no schema descriptions, the description does not sufficiently compensate. Lacks explanations for many parameters, no usage examples, and does not mention output schema. Incomplete for the tool's complexity.

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 0% (no descriptions), but the DAX template provides meaning for key parameters (date_table, date_column, window, granularity, base). However, other parameters like overwrite, measure_name, format_string, display_folder are not explained in the description.

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 'Create a trailing rolling average measure' which is a specific verb and resource, and distinguishes from other measure creation tools like pbi_create_measure or pbi_create_variance_measure.

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?

Implies usage for rolling average creation, but no explicit when-to-use or comparisons with alternative measure tools. Among many sibling tools for different measures, guidance is missing.

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