read_table_offline

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

With no annotations, the description carries the full burden and discloses the key side effect: 'Briefly opens the file in the local Power BI Desktop (a Desktop window appears), reads the rows, then closes Desktop.' It also reports the return behavior with truncated:true. It does not mention error handling or file-lock scenarios, but the essential operational traits are covered.

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 sentences, front-loaded with the action 'Read', and contains no redundant phrases. Every clause adds useful detail—row cap, closed-file requirement, Desktop behavior, return content, and truncation flag.

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?

For a tool with no output schema, the description adequately covers the return value ('columns + rows' and 'truncated:true') and the operational side effect of opening Desktop. It is concise but complete enough for the agent to invoke correctly. It could mention potential errors or prerequisites, but the core context is present.

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 100%, so baseline is 3. The description adds value by clarifying that pbixPath must point to a CLOSED .pbix, and by showing how topN and table are used in the EVALUATE TOPN expression. It also explains the truncated flag tied to topN, enriching the parameter semantics 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 starts with 'Read up to topN rows of one table from a CLOSED .pbix', providing a specific verb and resource. It clearly distinguishes itself from sibling tools by emphasizing the closed-file requirement and the temporary opening of Power BI Desktop, which makes its purpose uniquely clear.

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 explicitly states the tool is for CLOSED .pbix files and mentions that Desktop briefly opens, giving clear context for when to use it. However, it does not explicitly name alternative tools or state when not to use it, so it falls short of full exclusionary guidance.

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