pbi_create_import_query

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

The description is a single sentence that does not disclose any behavioral traits beyond the basic purpose. Annotations are absent, so the description carries full burden. It fails to mention side effects like modifications to existing tables, refresh behavior, or injection details.

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 overly concise to the point of being uninformative. It lacks any structure or additional context that would help the agent, such as examples or parameter highlights.

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?

Despite having an output schema and moderate complexity with 6 parameters, the description does not explain the output or provide enough context for correct invocation. The agent cannot determine what 'inject' means or what the resulting query will look like.

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 adds no meaning to the six parameters. It does not explain what 'table', 'excel_path', 'sheet_name', or optional parameters like 'refresh_after' mean, leaving the agent to rely solely on parameter names.

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 the tool generates and injects an Excel import Power Query for a table, which is a specific verb-resource combination. However, it does not distinguish from sibling tools like pbi_create_csv_import_query, which perform similar functions for different sources.

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?

No guidance is provided on when to use this tool versus alternatives such as pbi_create_csv_import_query or pbi_import_excel_workbook. There is no mention of prerequisites or context for usage.

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