pbi_model_info

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

No annotations are present, so the description must carry the behavioral disclosure burden. The description only says 'full model snapshot' without elaborating on performance, permissions, or what is included. It does not reveal potential risks or 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?

The description is a single sentence, which is concise and front-loaded. However, it lacks any structure (no paragraphs, bullet points) and may be too minimal for a complex tool. Every word earns its place, but more detail would improve usability.

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?

Although an output schema exists, the description does not set adequate context for the tool's scope. It fails to mention what the 'full model snapshot' includes (e.g., tables, measures, relationships), leaving ambiguity about the tool's comprehensive nature.

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 description coverage is 0%, meaning the input schema lacks parameter descriptions. The description does not mention or explain the parameters (include_hidden, include_row_counts). While parameter names are somewhat self-explanatory, the description adds no value to their meaning.

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 returns a 'full model snapshot in a single call.' This is a specific verb (return) and resource (full model snapshot), which distinguishes it from sibling tools like pbi_list_tables that return partial model info.

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 given on when to use this tool versus alternatives. With many sibling tools offering more targeted functionality (e.g., pbi_list_measures), the description should explicitly state when to use the full snapshot versus partial queries.

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