pbi_refresh_dataset

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

With no annotations, the description thoroughly discloses refresh types, commit modes, retries, timeout, table filtering, and polling behavior. However, it does not mention prerequisites (e.g., workspace/dataset existence) or rate limits.

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?

Well-structured with Args and Returns sections, front-loaded purpose. Some detail (e.g., API type explanation) is useful but could be slightly more concise without losing clarity.

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?

Covers all parameters, return format, and polling behavior comprehensively. Given the tool's complexity and absence of output schema in input, the description provides complete guidance 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?

Despite 0% schema description coverage, the description provides detailed explanations for all 10 parameters, including enums for refresh_type and commit_mode, format for timeout, and usage notes for tables. This fully compensates for missing schema descriptions.

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 triggers an Enhanced refresh for a Power BI dataset using the Enhanced Refresh API. Distinguishes itself from siblings like pbi_refresh_manage by specifying the API type and structured return details.

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 explains the enhanced refresh capability and when polling is beneficial, but does not explicitly compare to alternatives or state when not to use this tool versus other refresh methods.

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