pbi_convert_pbix_to_pbip

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

The description discloses non-obvious behavior: the tool opens Power BI Desktop to serialize the model because the .pbix model cannot be read directly, reuses an already-open Desktop session, closes Desktop if it opened it, and never modifies the original .pbix. It also warns about per-file time cost and dropped items. This goes well beyond the annotations.

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?

Dense but well organized: it moves from the core purpose to report/model behavior, then to parameter details, and finally to return information. Every sentence adds useful operational context; there is no filler.

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 is nearly complete for a complex tool with external side effects: it covers inputs, Desktop interaction, session reuse, non-destructiveness, live-connection requirements, and return contents. The main gap is that overwrite and desktop_timeout behavior are left to be inferred from schema defaults.

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?

With 0% schema description coverage, the description carries the parameter-documentation burden. It explains path, out_dir, recursive, include_model, close_desktop, and dataset_connection_string, and even warns that pbix_path/output_dir aliases do not exist. However, it leaves overwrite, project_name, request_id, and desktop_timeout undocumented, so the coverage is strong but not complete.

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 first sentence states the operation precisely: converting one or more .pbix files into .pbip projects (PBIR + TMDL). It explains what happens to the report and the model, which distinguishes it from inspection or project-creation siblings.

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 gives strong context for invocation: path accepts file or folder, recursive covers subfolders, out_dir creates one subfolder per report, include_model=false avoids touching Desktop, and dataset_connection_string is required for live connections. It does not explicitly name sibling alternatives or give a when-not-to-use rule, but the guidance is clear and practical.

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